We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
strange ssl problem with reverse proxy
strange ssl problem with reverse proxy
Solved pls see below reply i solved it hope it will help someone
Last edited by whoami on Sat Oct 03, 2020 8:48 am, edited 1 time in total.
Re: strange ssl problem with reverse proxy
never mind i solved it its about setting custom parameter in app.ini
god gogs default config sucks lol
after making these changes and restart gogs it worked perfectly
god gogs default config sucks lol
Code: Select all
PROTOCOL = https
EXTERNAL_URL = https://yourdomain.com/
CERT_FILE = /home/****/*****/ssl.crt
KEY_FILE = /home/******/****/ssl.key
HTTP_PORT = 3000
DISABLE_SSH = false
SSH_PORT = 22
START_SSH_SERVER = false
OFFLINE_MODE = false
-
- Posts: 5
- Joined: Fri Oct 16, 2020 5:04 pm
- Os: Ubuntu 17x
- Web: apache + nginx
Re: strange ssl problem with reverse proxy
Hi
I seem to have a similar problem, only that I don't know how to fix them:
- I have a web app running on http://mysub.domain.com:9000
- This url is the admin dashboard of the app
- This app shoots email with public facing URLs like http://mysub.domain.com:9000/xxx/xxx/xxx (which lead to an action within my app)
- The mysub.domain.com is SSL enabled and loads with SSL but the moment the port (9000) is added it returns error page and I have to access it via http
- The problem : 1 - port is visible to public and 2 - the URL shows insecure
- The solution required : 1 - port to be removed without the action of the URL to be impacted and the same URL needs to be served on SSL
Any help is appreciated.
I seem to have a similar problem, only that I don't know how to fix them:
- I have a web app running on http://mysub.domain.com:9000
- This url is the admin dashboard of the app
- This app shoots email with public facing URLs like http://mysub.domain.com:9000/xxx/xxx/xxx (which lead to an action within my app)
- The mysub.domain.com is SSL enabled and loads with SSL but the moment the port (9000) is added it returns error page and I have to access it via http
- The problem : 1 - port is visible to public and 2 - the URL shows insecure
- The solution required : 1 - port to be removed without the action of the URL to be impacted and the same URL needs to be served on SSL
Any help is appreciated.
Re: strange ssl problem with reverse proxy
Nor did I ever get their reverse proxy to function. I ended up using the letsencrypt linuxserver that has packaged nginx webserver and reverse proxy (and they even have a tonne of reverse proxy sample configurations for various docker containers). And SSL, which is good for remote access via https.jackdanielux wrote: ↑Fri Oct 16, 2020 5:10 pmHi
I seem to have a similar problem, only that I don't know how to fix them:
- I have a web app running on http: //mysub.domain.com:9000
- This url is the admin dashboard of the app
- This app shoots email with public facing URLs like https://canadaprimemarketing.com (which lead to an action within my app)
- The mysub . domain.com is SSL enabled and loads with SSL but the moment the port (9000) is added it returns error page and I have to access it via http
- The problem : 1 - port is visible to public and 2 - the URL shows insecure
- The solution required : 1 - port to be removed without the action of the URL to be impacted and the same URL needs to be served on SSL
Any help is appreciated.