I have multiple things running through a reverse proxy and I’ve never had trouble accessing them until now. The two hospitals are part of the same company, so their network setup is probably identical.

Curiously, it’s not that the sites can’t be found, but instead my browser complains that it’s not secure.

So I don’t think it’s a DNS problem, but I wonder what the hospital is doing to the data.

All I could come up with in my research is this article about various methods of intercepting traffic. https://blog.cloudflare.com/performing-preventing-ssl-stripping-a-plain-english-primer/

Since my domain name is one that requires https (.app), the browser doesn’t allow me to bypass the warning.

Is this just some sort of super strict security rules at the hospital? I doubt they’re doing anything malicious, but it makes me wonder.

Thanks!

Also, if you know of any good networking Lemmy communities, feel free to share them.

Admiral Patrick
link
fedilink
English
201M

I’ve only had that happen once on public wifi, and just assumed they were doing SSL stripping like you linked. I worked around it by connecting to my Wireguard VPN and routing my traffic through that.

Also, if you know of any good networking Lemmy communities, feel free to share them.

  • !networking@programming.dev
  • !networking@sh.itjust.works
walden
creator
link
fedilink
English
4
edit-2
1M

Thanks. Yup, wireguard makes it work. I forgot about that from the last time.

It’s still a little curious, though. The certs for my self hosted stuff are done the same was as for the Lemmy instance I’m posting from which I can browse with no problem. The only difference is Lemmy is hosted on Hetzner. Both are behind Nginx Proxy Manager.

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 279 users / day
  • 589 users / week
  • 1.34K users / month
  • 4.55K users / 6 months
  • 1 subscriber
  • 3.47K Posts
  • 69.3K Comments
  • Modlog