jk58730701
New member
- Joined
- Jul 20, 2020
- Messages
- 2
I always get confused when trying to get SSL running via an app on a specific port, rather than 443.
I am running a searx instance on a different VPS without directadmin and it is working fine. It is using a more simplified docker-compose.yaml than the official one and the web port is 3040.
In my apache conf file on my working setup i have this
ProxyPreserveHost On
ProxyPass / http://127.0.0.1:3040/
ProxyPassReverse / http://127.0.0.1:3040/
I searched and found information for adding custom httpd configuration. I tried to add this, but I must've done it incorrectly.
I also tried: https://help.directadmin.com/item.php?id=84 to create a domain that works as a reverse proxy to my DA instance. I wasn't able to get that working either, doing everything step-by-step.
Any help would be appreciated much. Thank you.
Edit:
Also, if I temporarily turn off the firewall, I am able to connect to the searx docker instance directly on port 3040 so i know it's working.
I am running a searx instance on a different VPS without directadmin and it is working fine. It is using a more simplified docker-compose.yaml than the official one and the web port is 3040.
In my apache conf file on my working setup i have this
ProxyPreserveHost On
ProxyPass / http://127.0.0.1:3040/
ProxyPassReverse / http://127.0.0.1:3040/
I searched and found information for adding custom httpd configuration. I tried to add this, but I must've done it incorrectly.
I also tried: https://help.directadmin.com/item.php?id=84 to create a domain that works as a reverse proxy to my DA instance. I wasn't able to get that working either, doing everything step-by-step.
Any help would be appreciated much. Thank you.
Edit:
Also, if I temporarily turn off the firewall, I am able to connect to the searx docker instance directly on port 3040 so i know it's working.
Last edited: