Thanks, eventually I went for the subdomain approach, it turned out to be a less headache and working just fine with wildcard letsencrypt ssl cert.
🤘linux, open source, metal
Thanks, eventually I went for the subdomain approach, it turned out to be a less headache and working just fine with wildcard letsencrypt ssl cert.
Thanks everyone, then I will go with the subdomain approach.
This is something I had as plan B 🙂 I’m not against it at all. 😃
I think your best bet would be to buy your own router and then use that one instead of the ISP provided router.
If you want to go more deeper, you can maybe choose one that is supported by OpenWrt. You can use the Table of hardware or the firmware selector to check if your desired router has OpenWrt support.
fost.hu, lol, nice one 😃
fost.hu, lol, nice one 😃
Check out this post: https://lemmy.world/post/538280
Here’s a howto for your case. In the end it should be like ‘ngrok tcp 32400’. You can try it out, while you’re searching for a VPS 🙂
I never used it, but I bumped into ngrok when I was researching remote accessing services hosted behind CGNAT, and it turned out to be not needed in my case, but maybe it’s worth for you to check it out: https://ngrok.com/docs/using-ngrok-with/cgnat/
I installed OpenWrt on my home router and set up wireguard on it. If you have dinamic IP address assigned by your ISP, like me, you also have to setup a dynamic dns updater on the router. I use duckdns.org. Then you have to open the port for wireguard on the router. Here’s a video guide on how to do it: https://www.youtube.com/watch?v=Bo2AsW4BMOo