Recherche avancée

Sur d’autres sites (6024)

• nginx : [emerg] invalid port in url "http://192.168.0.100:80/live" in nginx.conf - Restreaming OBS to LAN

  17 novembre 2018, par popek069

  I want to restream OBS to LAN. So I set up nginx server. The server receive stream from OBS using RTMP and restreams it to HTTP to view from another device.
  Streaming from OBS works, but when I start nginx I get an error

  PS C:\Users\popek\Downloads\nginx> .\nginx.exe -s reload
  
  nginx: [emerg] invalid port in url "http://192.168.0.100:80/live" in C:\Users\popek\Downloads\nginx/conf/nginx.conf:187

  I’m new to nginx and I’m running Windows 10, nginx server and OBS are on the same pc with ip 192.168.0.100
  I’d like to also reencode stream using ffmpeg if it’s possible. I know ffmpeg, I don’t know only how to set input and output.

  Config : (nginx.conf)

  #user  nobody;
  
  # multiple workers works !
  
  worker_processes  2;
  
  
  
  #error_log  logs/error.log;
  
  #error_log  logs/error.log  notice;
  
  #error_log  logs/error.log  info;
  
  
  
  #pid        logs/nginx.pid;
  
  
  
  
  
  events {
  
      worker_connections  8192;
  
      # max value 32768, nginx recycling connections+registry optimization = 
  
      #   this.value * 20 = max concurrent connections currently tested with one worker
  
      #   C1000K should be possible depending there is enough ram/cpu power
  
      # multi_accept on;
  
  }
  
  
  
  
  
  http {
  
      #include      /nginx/conf/naxsi_core.rules;
  
      include       mime.types;
  
      default_type  application/octet-stream;
  
  
  
      #log_format  main  '$remote_addr:$remote_port - $remote_user [$time_local] "$request" '
  
      #                  '$status $body_bytes_sent "$http_referer" '
  
      #                  '"$http_user_agent" "$http_x_forwarded_for"';
  
  
  
      #access_log  logs/access.log  main;
  
  
  
  #     # loadbalancing PHP
  
  #     upstream myLoadBalancer {
  
  #         server 127.0.0.1:9001 weight=1 fail_timeout=5;
  
  #         server 127.0.0.1:9002 weight=1 fail_timeout=5;
  
  #         server 127.0.0.1:9003 weight=1 fail_timeout=5;
  
  #         server 127.0.0.1:9004 weight=1 fail_timeout=5;
  
  #         server 127.0.0.1:9005 weight=1 fail_timeout=5;
  
  #         server 127.0.0.1:9006 weight=1 fail_timeout=5;
  
  #         server 127.0.0.1:9007 weight=1 fail_timeout=5;
  
  #         server 127.0.0.1:9008 weight=1 fail_timeout=5;
  
  #         server 127.0.0.1:9009 weight=1 fail_timeout=5;
  
  #         server 127.0.0.1:9010 weight=1 fail_timeout=5;
  
  #         least_conn;
  
  #     }
  
  
  
      sendfile        off;
  
      #tcp_nopush     on;
  
  
  
      server_names_hash_bucket_size 128;
  
  
  
  ## Start: Timeouts ##
  
      client_body_timeout   10;
  
      client_header_timeout 10;
  
      keepalive_timeout     30;
  
      send_timeout          10;
  
      keepalive_requests    10;
  
  ## End: Timeouts ##
  
  
  
      #gzip  on;
  
  
  
      server {
  
          #listen       80;
  
          server_name  localhost;
  
  
  
          #charset koi8-r;
  
  
  
          #access_log  logs/host.access.log  main;
  
  
  
          ## Caching Static Files, put before first location
  
          #location ~* \.(jpg|jpeg|png|gif|ico|css|js)$ {
  
          #    expires 14d;
  
          #    add_header Vary Accept-Encoding;
  
          #}
  
  
  
  # For Naxsi remove the single # line for learn mode, or the ## lines for full WAF mode
  
          location / {
  
              #include    /nginx/conf/mysite.rules; # see also http block naxsi include line
  
              ##SecRulesEnabled;
  
                ##DeniedUrl "/RequestDenied";
  
                ##CheckRule "$SQL >= 8" BLOCK;
  
                ##CheckRule "$RFI >= 8" BLOCK;
  
                ##CheckRule "$TRAVERSAL >= 4" BLOCK;
  
                ##CheckRule "$XSS >= 8" BLOCK;
  
              root   html;
  
              index  index.html index.htm;
  
          }
  
  
  
  # For Naxsi remove the ## lines for full WAF mode, redirect location block used by naxsi
  
          ##location /RequestDenied {
  
          ##    return 412;
  
          ##}
  
  
  
  ## Lua examples !
  
  #         location /robots.txt {
  
  #           rewrite_by_lua '
  
  #             if ngx.var.http_host ~= "localhost" then
  
  #               return ngx.exec("/robots_disallow.txt");
  
  #             end
  
  #           ';
  
  #         }
  
  
  
          #error_page  404              /404.html;
  
  
  
          # redirect server error pages to the static page /50x.html
  
          #
  
          error_page   500 502 503 504  /50x.html;
  
          location = /50x.html {
  
              root   html;
  
          }
  
  
  
          # proxy the PHP scripts to Apache listening on 127.0.0.1:80
  
          #
  
          #location ~ \.php$ {
  
          #    proxy_pass   http://127.0.0.1;
  
          #}
  
  
  
          # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
  
          #
  
          #location ~ \.php$ {
  
          #    root           html;
  
          #    fastcgi_pass   127.0.0.1:9000; # single backend process
  
          #    fastcgi_pass   myLoadBalancer; # or multiple, see example above
  
          #    fastcgi_index  index.php;
  
          #    fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
  
          #    include        fastcgi_params;
  
          #}
  
  
  
          # deny access to .htaccess files, if Apache's document root
  
          # concurs with nginx's one
  
          #
  
          #location ~ /\.ht {
  
          #    deny  all;
  
          #}
  
      }
  
  
  
  
  
      # another virtual host using mix of IP-, name-, and port-based configuration
  
      #
  
      #server {
  
      #    listen       8000;
  
      #    listen       somename:8080;
  
      #    server_name  somename  alias  another.alias;
  
  
  
      #    location / {
  
      #        root   html;
  
      #        index  index.html index.htm;
  
      #    }
  
      #}
  
  
  
  
  
      # HTTPS server
  
      #
  
      #server {
  
      #    listen       443 ssl spdy;
  
      #    server_name  localhost;
  
  
  
      #    ssl                  on;
  
      #    ssl_certificate      cert.pem;
  
      #    ssl_certificate_key  cert.key;
  
  
  
      #    ssl_session_timeout  5m;
  
  
  
      #    ssl_prefer_server_ciphers On;
  
      #    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
  
      #    ssl_ciphers ECDH+AESGCM:ECDH+AES256:ECDH+AES128:ECDH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!eNULL:!MD5:!DSS:!EXP:!ADH:!LOW:!MEDIUM;
  
  
  
      #    location / {
  
      #        root   html;
  
      #        index  index.html index.htm;
  
      #    }
  
      #}
  
  
  
  }
  
  
  
  
  
  rtmp {
  
          server {
  
                  listen 1935;
  
                  chunk_size 4096;
  
  
  
                  application live {
  
                          live on;
  
                          record off;
  
                          hls on;
  
                          push http://192.168.0.100:80/live ;
  
                  }
  
          }
  
  }

• Secure and track every change to your Matomo installation with the Activity Log plugin

  14 novembre 2017, par InnoCraft — Plugins

  Are you wondering how your colleagues are using Matomo (Piwik) ? Would you like to know if an unauthorized user got an access to your installation ? Would you like to remember the last actions you performed in Matomo some weeks ago ? At InnoCraft, we developed a plugin called “Activity Log”. With this feature you can easily track and check all major changes to your Matomo websites, for example : user permissions, goals, and funnels. In this article we will show you the different ways you can use it and explain why it is an invaluable plugin.

  Activity log for better security

  The activity log feature has been designed for security. Also referred to as “audit logging” or “audit trail”, with this plugin you will be able to :

  1. detect any suspicious actions
  2. detect hacker attacks
  3. help identify performance problems
  4. see clearly who did what, and when
  5. find out how people are using Matomo (Piwik) within your company

  1 – detect any suspicious actions

  With audit trail you can easily identify if a former employee still has access to your Matomo (Piwik) installation. You will then be able to know when he accessed it for the last time, and what changes she or he performed. If you got hacked, you will be able to find out if the user created, changed, or deleted any website, goals, or did anything else suspicious.

  2 – detect hacker attacks

  When an unregistered user is trying to access your Matomo (Piwik), each failed login attempt is registered within the Activity Log report.

  3 – help identify performance problems

  Activity Log can help you identify performance problems by registering the sequence of each major action a user performed. For example, if a user updated or installed a third party plugin, and suddenly Matomo (Piwik) is getting performance problems, then it is likely that the plugin update caused it.

  4 – see clearly who did what, and when

  It is always challenging in an organization to know who did what and when. With Activity Log, you will know who were the employee(s) that accessed Matomo (Piwik), created, updated, or deleted a goal, a funnel, a scheduled report, and much more.

  5- find out how people are using Matomo within your company

  By having a look at how people are using Matomo (Piwik) you will have an overview of how your colleagues use Matomo. For example, you can see who is creating Custom segments to analyse the audience in more details, who is creating funnels to learn where your users drop off. You will then be able to identify who has the knowledge and who needs training.

  Did you know ?

  You can help the Matomo (Piwik) core team make Matomo even better by sharing anonymously how you use Matomo on a day to day basis. You just need to install the following plugin : http://plugins.matomo.org/AnonymousPiwikUsageMeasurement

  What’s in it ?

  Once downloaded and installed from the marketplace, you will be able to access the activity log from the admin panel within the diagnostic section :

  

  If you are logged as a super user administrator, you will get an overview and a detailed report about who accessed Matomo (Piwik) and which actions they performed.

  Those reports are critical as they allow the super user to :

  • ensure users are following all documented procedures within your organization such as naming conventions for reports, using the right settings when adding measurables…
  • identify suspicious behavior. As those reports are gathering all major Matomo (Piwik) users activities it is easy to identify non conventional behavior.
  • replay the sequence some users went through in order to fix any potential issues.

  Activity log view report you can access through the admin panel

  So you will see in a second if an unusual user got access to Matomo (Piwik) and the different actions the user performed.
  It is also a good way to see the features that your users are using and identify potential misuse.

  As a regular user or admin, activity log is providing only the historical actions that this user performed :

  

  Actions listed in the log include any changes (add, edit, delete) to the following features (this is a non exhaustive list) :

  • Annotation
  • Custom Alert
  • Custom Dimension
  • Goal
  • Privacy settings
  • Scheduled report
  • Segment
  • User
  • Website
  • …

  This is a ideal to remember the actions they previously performed some weeks/months ago.

  Where can I start from here ?

  Activity log is a premium feature you can acquire through the Matomo (Piwik) marketplace. If you want to experience it before purchasing it, you can try it for free on our cloud infrastructure.

  I want to try the Activity Log plugin

  Activity log is just one out of the many great premium features developed by InnoCraft, the company founded by the creators of Matomo. Discover all their special plugins through the premium marketplace.

   

• Secure and track every change to your Piwik installation with the Activity Log plugin

  14 novembre 2017, par InnoCraft — Plugins

  Are you wondering how your colleagues are using Piwik ? Would you like to know if an unauthorized user got an access to your installation ? Would you like to remember the last actions you performed in Piwik some weeks ago ? At InnoCraft, we developed a plugin called “Activity Log”. With this feature you can easily track and check all major changes to your Piwik websites, for example : user permissions, goals, and funnels. In this article we will show you the different ways you can use it and explain why it is an invaluable plugin.

  Activity log for better security

  The activity log feature has been designed for security. Also referred to as “audit logging” or “audit trail”, with this plugin you will be able to :

  1. detect any suspicious actions
  2. detect hacker attacks
  3. help identify performance problems
  4. see clearly who did what, and when
  5. find out how people are using Piwik within your company

  1 – detect any suspicious actions

  With audit trail you can easily identify if a former employee still has access to your Piwik installation. You will then be able to know when he accessed it for the last time, and what changes she or he performed. If you got hacked, you will be able to find out if the user created, changed, or deleted any website, goals, or did anything else suspicious.

  2 – detect hacker attacks

  When an unregistered user is trying to access your Piwik, each failed login attempt is registered within the Activity Log report.

  3 – help identify performance problems

  Activity Log can help you identify performance problems by registering the sequence of each major action a user performed. For example, if a user updated or installed a third party plugin, and suddenly Piwik is getting performance problems, then it is likely that the plugin update caused it.

  4 – see clearly who did what, and when

  It is always challenging in an organization to know who did what and when. With Activity Log, you will know who were the employee(s) that accessed Piwik, created, updated, or deleted a goal, a funnel, a scheduled report, and much more.

  5- find out how people are using Piwik within your company

  By having a look at how people are using Piwik you will have an overview of how your colleagues use Piwik. For example, you can see who is creating Custom segments to analyse the audience in more details, who is creating funnels to learn where your users drop off. You will then be able to identify who has the knowledge and who needs training.

  Did you know ?

  You can help the Piwik core team make Piwik even better by sharing anonymously how you use Piwik on a day to day basis. You just need to install the following plugin : http://plugins.piwik.org/AnonymousPiwikUsageMeasurement

  What’s in it ?

  Once downloaded and installed from the marketplace, you will be able to access the activity log from the admin panel within the diagnostic section :

  

  If you are logged as a super user administrator, you will get an overview and a detailed report about who accessed Piwik and which actions they performed.

  Those reports are critical as they allow the super user to :

  • ensure users are following all documented procedures within your organization such as naming conventions for reports, using the right settings when adding measurables…
  • identify suspicious behavior. As those reports are gathering all major Piwik users activities it is easy to identify non conventional behavior.
  • replay the sequence some users went through in order to fix any potential issues.

  Activity log view report you can access through the admin panel

  So you will see in a second if an unusual user got access to Piwik and the different actions the user performed.
  It is also a good way to see the features that your users are using and identify potential misuse.

  As a regular user or admin, activity log is providing only the historical actions that this user performed :

  

  Actions listed in the log include any changes (add, edit, delete) to the following features (this is a non exhaustive list) :

  • Annotation
  • Custom Alert
  • Custom Dimension
  • Goal
  • Privacy settings
  • Scheduled report
  • Segment
  • User
  • Website
  • …

  This is a ideal to remember the actions they previously performed some weeks/months ago.

  Where can I start from here ?

  Activity log is a premium feature you can acquire through the Piwik marketplace. If you want to experience it before purchasing it, you can try it for free on our cloud infrastructure.

  I want to try the Activity Log plugin

  Activity log is just one out of the many great premium features developed by InnoCraft, the company founded by the creators of Piwik. Discover all their special plugins through the premium marketplace.