New answers tagged

-1

Sure you could handle it with a load balancer. But the appropriate way is to use Server Name Indication (SNI). Don't reinvent the wheel, especially in network/internet questions...


0

The solution for me was to set the /home/user/public_html permissions to 755. By default, it was being created with 751 permissions. This was blocking the nginx user from being able to 'read' it. Certain web hosting panels like VestaCP, CPanel, and others may inadvertently do this when adding a new site through their interface. Solution: sudo chmod 755 ~/...


2

This is entirely up the server and how it has been configured. Most servers are not intelligent enough to know what to push and depend on being configured. So you can set up config to say if any index.html file is requested then push common.css and common.js. It’s important then to consider the next page that’s visited - there is no need to push those files ...


1

Assuming the 'standard' config, ssl_access_log and ssl_request_log are written (in slightly different formats) for each HTTP request received on the TLS vhost. If the certificate is rejected, there is no TLS connection and it is not possible to send any HTTP request, so there is nothing to log. Depending on the client program and TLS library it uses, it may ...


1

For free Gmail, the daily limit sending via SMTP is 100 messages per rolling 24 hours. (NOT per day). If you want to send 1000 emails per day, it's impossible. reference For G Suite, messages per day is 2000, so you can use it if you only send 1000 emails per day. reference The other reasons that why I don't recommend use Gmail as SMTP are: Based on my ...


1

No, it is not logged on the server. This check is made on the client, there is no way to know for the server if this problem occured or not. You can (and should) configure a default VirtualHost that catches all requests to domains not matching your "real" VirtualHosts. That way you can find out if requests to your server are made with other ...


2

Just found the answer: ProxyPreserveHost On https://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxypreservehost


0

While the mentions above make very clear that DNS records are port agnostic (except for SRV records -- that are not incorporated in most clients); there is a possibility: to use URL forwarding services that are offered by most DNS providers (eg. easyDNS) This will allow you to make easier for the user: so from your exemple www.example.com goes to port 87, ...


2

Delete the wildcard DNS entry from your DNS records. Create records only for those subdomains which you intend to be accessible.


Top 50 recent answers are included