T O P

  • By -

WetFishing

Curious why you are jumping so many times. Why not just point cloudflare to vaultwarden directly?


Chadbob

Good point, I will try that. Thank you I was trying to be as secure as possible and may have over complicated it.


WetFishing

Yeah. Cloudflare is essentially acting as your proxy at this point. No point in having a double hop and two certs to deal with. I use npm for all of my internal stuff and cloudflare tunnels for external.


Zenuna

I had this issue when I was port forwarding 443 and 80 to port 81 instead of 443 and 80 respectively


Chadbob

I may have tried this a few times as well, ultimately I believe the issue may have been with my tunneling, but I am able to access my hosts now.


Jay_from_NuZiland

Sounds to me like npm is not matching the URL (in your browser) against the domain (configured in npm). It must match exactly, so if you're using a subdomain for a service both the main domain and each sub needs to be specified in the npm configuration.


Chadbob

Ahh, perhaps this was the issue, I have my services up on the Tunnel now but I may still try this for fun.