New answers tagged

0

I got it working this is needed in Ngingx reverse proxy config file server { server_name testibot1.omnia.fi; index index.php index.html index.htm index.nginx-debian.html; root /var/www/public_html/testibot1; location / { proxy_pass http://testibot1.omnia.fi:444; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For ...


0

The cause of the issue is literally printed in the browser's developer console: Therefore, you need to make XHR requests happening over HTTPS connection. You probably want to add another location to the nginx configuration: location /socket.io { proxy_pass http://localhost:5006; } while also changing the URL in the frontend configuration: socketUrl: ...


0

You need a certificate that has the servername without FQDN as an SAN. This is the only way to prevent certificate errors when the server is accessed without the FQDN. You can do that pretty easy by creating your own Certificate Authority (CA). A simple CA can be created with tools like Easy RSA. After creating the CA certificate you need to deploy the CA ...


2

Ok, I figured out my problem. I was previously using /etc/apache2/sites-enabled/domain, but I needed to change it to /etc/apache2/sites-enabled/domain.conf.


0

I believe this is now the way to go solving the original problem: proxy_set_header X-SSL-CERT $ssl_client_escaped_cert; According to the docs: $ssl_client_escaped_cert returns the client certificate in the PEM format (urlencoded) for an established SSL connection (1.13.5);


0

You can use server variables to log a CERT_COOKIE (unique identifier) and the incoming subject and the issuer subject of the certificate. However, the CERT_Cookie is generated by IIS and does not contain the thumbprint. Possible values in the advanced logging (logging tools) settings: https://docs.microsoft.com/en-us/iis/web-dev-reference/server-variables (...


0

Not tested on AWS, however I solved with this line in each location block: proxy_redirect ~^http:(.*)$ https:$1;


1

This is an example from docs for req_ssl_sni: tcp-request inspect-delay 5s tcp-request content accept if { req_ssl_hello_type 1 } use_backend bk_allow if { req_ssl_sni -f allowed_sites } default_backend bk_sorry_page You probably need tcp-request inspect-delay set to something, because not setting it, means haproxy doesn't wait at all and has no idea what ...


Top 50 recent answers are included