I switched to it because the ISP blocked ports 80/443. It was good and things actually got a bit faster with them handling SSL certs.
but one thing to note is that the free tier has a 100MB file limit. I got around some of that by using the tail scale vpn with a custom domain entry to point to the local network.
I did these changes (wire guard to tail scale, dns to tunnels, etc) at different times, which is why things aren’t very consistent.
if you’re on your home network the address will be the IP address and, if you’re not using a reverse proxy, the port the app runs on.
with reverse proxy: http/s://192.168.8.2 or whatever without: http/s://<IP address>:3000 or whatever the port is
filled! I’m looking forward to the results!
I can’t
Cloudflare tunnels - it used to be dynamic dns, but the ISP blocked ports 80/443, so I switched to tunnels.
External DNS on the Gl-Inet router, included with the product
Goodcloud, from Gl-Inet (included and really nice to have another way to get to it)
for the home self-hosting, that’s pretty much it.
For the (coming soon TM) fediverse apps in Keyboard Vagabond, add in S3, cloudflare CDN
in addition to the other suggestions of checking the rame stick, do you have resource limits on your containers? It’s generally a good thing to have anyway, but I’d do that after checking the ram and cooling situation. Check your cpu temps as well.
oh that’s a shame :(
there is the fb Lite app, which is mainly for places without good Internet. That one is supposed to not do the same kind of tracking as the main app, at least when it’s closed. I can’t say the same for messenger though
the ISP blocked my ports and cloudflare got me around it. I’ll accept the compromise ;)
cloudflare happened first and I haven’t been bothered to change it yet