Using apache2 as proxy with certbot ssl creates broken login

zeLostchild commented 5 years ago

When I login from the actual ip it works or when it is not using https.

I tried a using certbot with apache and well... this is essentially what I got when I try in login an error occurs. (I can still use IP address to login)

Here is my apache .conf file

<IfModule mod_ssl.c>
<VirtualHost *:443>
   ProxyPreserveHost On
   ServerName pond.mydomain.org
     ProxyPass / http://0.0.0.0:8882/
     ProxyPassReverse / http://0.0.0.0:8882/

Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/pond.mydomain.org/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/pond.mydomain.org/privkey.pem
</VirtualHost>
</IfModule>

Also I have EXTERNAL_HOSTNAME=pond.mydomain.org for libretime.

Is there something that i need to add to the apache2 .conf file?

Fireant456 commented 4 years ago

I am having the same issue using HAProxy and running into the same issue. Seems something with apache on the core container isn't getting set up right just changing apache port to 80 and supplying the hostname.

lord-carlos commented 4 years ago

I got the same problem with Nginx. Nothing showing up in the logs.

medcelerate commented 4 years ago

Did you check the zendphp logs? I had a similar issue and it was due to CORS.

lord-carlos commented 4 years ago

Did you check the zendphp logs? I had a similar issue and it was due to CORS.

That was it. Thank you.

maxlinux2000 commented 3 years ago

Hi How to fix the problem with CORS? I'm using traefik 1.7.

lord-carlos commented 3 years ago

Hi How to fix the problem with CORS? I'm using traefik 1.7.

Via ip login, go to preference, scroll down to Allowed CORS URLs and enter your domain or domains there. With http:// or https://

ned-kelly / docker-multicontainer-libretime

Using apache2 as proxy with certbot ssl creates broken login #27