Learn how to run the Laravel Websockets package in Laravel and deploying it to a Forge provisioned server with SSL.
Guide on how to secure a NGINX vhost with a Let’s Encrypt certificate.
Since Chrome is soon dropping HTTP/2 via NPN we need to support HTTP/2 via ALPN, however… on Ubuntu 14.04 NGINX has been compiled with OpenSSL 1.0.1 which does not support ALPN :( So let’s fix that! First we need to upgrade OpenSSL, since that is not that easy to do ourselfs I use the package repository provided by Ondřej Surý for originally PHP but also includes a up-to-date OpenSSL package.
Sometimes you want to store the user id with the session so you can purge all sessions or even a single session creating a more secure system for your users, or maybe you want to see how many times a user is logged in. There are many use cases but it’s not possible by default… so let’s implement this nifty feature :) Note: this is not needed in Laravel 5.
Since this article I have bought a special domain for it and rebranded it to: Server Chief I manage a bunch of server, each week I have to SSH in each and every one of them to update packages, check their disk usage and do a bunch of maintenance stuff. This is a lot of work 🙁 So I thought, hey! This can be much easier if I had a tool that would SSH in for me and execute the commands for me and report the output back so I only have to login to servers that have errors and I can easily scan through the output (and look back at earlier executions to see if something has changed).
With dnsmanager.io you can easily manage the DNS records of all your domain names on an battle tested premium service. Domains can be easily (in bulk) created and edited with predefined templates or through our simple API (or using one of our integrations with for example Plesk as an extension). Our webinterface is multilangual (English and Dutch) and has 15 themes to choose from. It is also possible to use our whitelabel nameservers and reseller functionality to deliver our DNS service to your customers, with the API your customer can’t even tell we got your back.
FTP passive mode require some or all unprivileged (1024-65534) ports to be accessible by the world. By default Plesk does not add a rule for these ports, so passive mode does not work. To enable passive mode we need to edit the ProFTPD (FTP server used by Plesk) configuration. Edit the config file (located here: /etc/proftpd.conf) with your favorite shell editor (like nano or vim). Find the <global> section and add the following rule between the <global> and </global> tags: