If you don’t want to mess with SSL you can do the same with port 80.
Comment on Question about accessing my services from corporate Network
jeena@piefed.jeena.net 3 weeks ago
Just use port 443 or 80 and use sub domains and a reverse proxy for each of your services.
For example:
https://rss.example.com goes to port 443 on your server where you run a nginx with letsencrypt. You set up a vhost for this subdomain which then internally proxies to your IP adress and port for freshrss.
I have it like that: https://rss.jeena.net and https://piefed.jeena.net and https://toot.jeena.net and so on.
jeena@piefed.jeena.net 3 weeks ago
ChapulinColorado@lemmy.world 3 weeks ago
But then you are sending credentials in clear text over the network. That will get logged on the corporate access logs ensuring a quick permanent vacation once they notice how careless the employee is, not to mention the mixing if personal and work resources.
k4j8@lemmy.world 3 weeks ago
I do this too plus block all IPs via firewall except my work and home IP addresses.
stratself@lemdro.id 3 weeks ago
Beat me to it. This is likely the best way as 443 is ubiquitously unblocked on most networks