Recherche avancée

Sur d’autres sites (6667)

• 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 ;
  
                  }
  
          }
  
  }

• Presentation of Piwik’s collaborative translations platform : oTrance [Interview]

  19 avril 2013, par matt — Community, translation

  Piwik enables domain administrators, hobbyists, power users, personal website builders and everyone in between to access enormous amounts of data for website analytics. To support all those users, Piwik needs to be available in a number of different languages. From the start, we made internationalization (i18n) part of Piwik’s DNA. There are now dozens active volunteers who help make sure each language is well represented in the latest official release of Piwik. As of now, Piwik is available in 48 languages.

  Recently a new tool became available that makes the translation of Piwik much easier. The software we are using is an open source platform called oTrance. It has made our translation architecture more robust, and it allows us to expedite the timely delivery of high quality and up-to-date translations to the thousands of people who rely on Piwik every day.

  We’ve met with oTrance creator and lead developer Daniel Schlichtholz who answered a few questions for us.

  1. What is oTrance ?
  2. What sets oTrance apart from the other ways to manage translations ?
  3. Now that oTranCe 1.0 is out, what will you be working on next ?

  What is oTrance ?

  oTranCe is the short form of “Online Translation Center”. It was born because I needed a translation platform for my project MySQLDumper.

  Many languages have been added by the community and manual maintenance became more and more time consuming. I wanted to change that. So I searched for an existing platform I could use and tested a lot of approaches. To put a long story short : none of the given solutions satisfied my needs.

  From the view of a translator maintaining a language should be as easy as possible. In most cases they have to install a program on their local machine or the workflow was too difficult. A translator doesn’t want to struggle with technical things ; he just wants to translate the phrases and wants to know the progress.

  That’s the main goal we want to reach : to make the translation process as easy as possible.

  What sets oTrance apart from the other ways to manage translations ?

  Ease of use is one advantage of oTranCe compared to other solutions. Another advantage is that project administrators can install oTranCe on their own server – so nobody is dependant of a third party provider.

  We love to get feedback from other users. User feedback influences the way oTranCe is developed. We believe that this way oTranCe satisfies the requirements of the real world.

  We also have extensive user documentation, in our “Working with oTranCe” wiki. We try to document use cases in an understandable way. We don’t write down marketing buzz words, but try to explain the use from the view of the user/administrator.

  Now that oTranCe 1.0 is out, what will you be working on next ?

  The language files can be exported to version control and oTranCe can commit changes to the target repository. Currently we support export to Subversion, and we are working on a Git export adapter, which will be released soon.

  Another issue we are trying to solve is the context problem. When your project uses many different phrases the translator often doesn’t know in which context the current phrase is used. Version 1.1.0 (not released yet, but you can grab the latest developer version from GitHub) introduces the oTranCe-connector. The idea behind it : a small plug in grabs the used phrases/keys on the current page, and on click this list is submitted to oTranCe, where the translator can edit the words. This way the translator knows in which context these phrases are used. I wrote a small plug in for OXID eShop. Since it is really easy to implement, my hope is that other plug ins for other applications will be added by the community.

  Matthieu : Congratulations Daniel for having created such an awesome Translation Platform. At Piwik we are really thankful for oTranCe, which has resulted in much better translation process, and happier translators. Keep up the good work !

  If you are a Piwik user, and if you want to participate in translating Piwik, please sign up for an account on oTrance and become part of the team making Piwik available in more languages across the world.

• Piwik SSO options and why is it useful ?

  8 novembre 2017, par Piwik Core Team — Plugins

  Bored with typing again and again different logins and passwords for each service you have access to ? Would you like to add hundreds or thousands of users with different roles to your Piwik at once ? Would you like to save time and effort of managing your users while increasing the security in your business ? Guess what, Piwik has come up with great features to do just that.

  But what is a SSO ?

  Before introducing you to new Piwik features, let me explain what a SSO is.
  SSO is the acronym for Single Sign On. As its name suggests this authentication process allows a user to access multiple applications with one set of login credentials.

  Advantages of using a SSO are numerous :

  • improving security, for example when an employee is leaving your company, how can you check that all his credentials have been removed ?
  • reducing employees time-wasters such as having to enter logins/passwords each time.
  • providing a centralized database for administrators. They can then easily manage permissions of all employees saving them heaps of time.
  • reduces support costs related to authentication / accounts management.

  In order to provide SSO options, two Piwik plugins have been developed and are available on the marketplace :

  • SAML
  • LDAP

  SAML

  

  SAML stands for “Security Assertion Markup Language”, it is a standard in order to exchange authentication and authorization between an identity provider (OneLogin, Okta, Ping Identity, ADFS, Google, Salesforce, SharePoint…) and a service provider.
  An identity provider is an online service that authenticates users on the Internet by using security tokens.

  Are you wondering if your business or organization is using any of these providers ? We recommend to ask your operations team or sysadmin.

  At InnoCraft, we developed a plugin in order to allow SSO with SAML for Piwik. It can ensure consistent access control across the enterprise and external providers, potentially reducing support costs related to authentication and accounts management.

  The installation process is straightforward. All you need is to get the SAML premium feature from the marketplace. Once installed, you will access the SAML configuration interface through the admin where you can configure various settings :

  • SAML Status
  • Identity Provider (Entity ID, SSO endpoint info, Public x509 certificate)
  • Just-in-time provisioning and Mapping attributes
  • Access Synchronization
  • Advanced settings

  

  From there you will need to follow our detailed documentation to have it up and running :
  https://piwik.org/docs/login-saml/.
  Once finished, you will then be able to use SAML to authenticate to your Piwik account :

  

  As all premium features, SAML is eligible to a 30-day period money back guarantee, so do not hesitate to have it a try.

  LDAP

  

  LDAP stands for Lightweight Directory Access Protocol. As its names implies LDAP is a directory, hosted on a server, which organizes the data about people in your company.
  Thanks to the LDAP plugin, Piwik can be connected to your LDAP infrastructure and then use all its power in order to give each individual an access with different rights according to their needs.

  Let’s say that you have 1,000 employees within a company and they all need right now an access to the analytics reports in Piwik with different roles. This is what LDAP can do.

  Moreover if your business or organization is already using LDAP, we recommend using the LDAP connector for Piwik for better security, to stop wasting time of your users and sysadmins, and to reduce the costs related to account management.

  You understood it well. LDAP is a plugin which saves a LOT of time within an organization. Here is a preview of the settings part :

  

  LDAP has been developed by the Piwik core team and is available as a Free plugin on the marketplace.

  Try it now within the marketplace

  If you are surprised by the possibilities that Piwik is offering in terms of plugins, the good news is that many other plugins are waiting for you on the marketplace. Check out our premium marketplace which offers state-of-the-art plugins to get the most out of Piwik.

  And if you are a developer feel free to create your own plugin, a detailed documentation is available at : https://developer.piwik.org/guides/getting-started-part-1.