Forum archive
Change Port 80 to Port 81 OTRS
I am running TKL Simple Invoices on port 80 behind a cheap netgear "router". I would like to run TKL OTRS on port 81 so I can use port forwarding to access both from a remote location.
I have tried changing both in the virtual host (sites-available) and the ports.conf. I was succesful in getting the web server to listen to 81, except I get an ssl error when trying to login to OTRS. I can't recall the error, but it was something to do with the ssl key not matching.
Is there a proper sequence of steps to change over to port 81 for the webserver.
Thanks,
Eric
Replies (3)
Perhaps the easiest way...
Reply 1Sorry for the slow response...
Reply 2I missed your post... Anyway...
If you want to connect to your server via HTTPS then try forwarding to port 443 (instead of 80). 80 is the default HTTP port (and will reject HTTPS), 443 is the default HTTPS. And you can use any port you like (that isn't already assigned) as the incoming port on the router...
TBH you mention you are running Simple Invoices on 80... Personally I'd be running that on HTTPS too!
i tried...
Reply 3Jeremy,
I configured the router to take the incoming port 81 and forward to port 80 on the server as you suggested. That does work.. almost.
You are right about the https. The only way I was able to load the login to OTRS was to drop the https. I do not want to do that since I will be passing customer information.
I do not fully understand how the SSL certs work, so for now I will try to do a install of OTRS or osTickets on my server running Simple Invoices. I can use a cname and virtualhosts and not worry about different external and internal ports.
Thanks for the reply. This is something I want to revisit later when I have more time.
Thanks,
Eric
Is to just use your router's NAT configuration to reroute WAN port 81 to LAN port 80. Then no modification is required to the appliance itself... Although some routers do not support that (but I think most do these days...)
One other thing to keep in mind is that an encrypted connection (i.e. HTTPS) is preferable. Although it sounds like you have reconfigured the HTTPS port rather than the HTTP port? HTTP (port 80) doesn't use SSL certs... And with a self signed SSL cert it is expected behaviour to get an SSL error (because the certificate hasn't been created by an approved thrid party). Firefox will allow you to save self-signed certs whereas Chrome will always throw that error...
If my answer is a complete miss then perhaps post with some more specific info (i.e. the exact error you are getting and where you are getting it (in the appliance logs or in your web browser...?)