Roxedus

They both do the work, and cater to different scenarios. My reasoning for my suggestion is that I dont want to be able to reach /admin at all with my reverse proxy. Another thing to think about is the resulting error code, where my suggestion gives a 404, while the deny gives a 403. A 403 might say to a potential attacker that there is something there (you could have it respond with a 404 instead)

If it is anything like the iOS app, if keeps its own chain of certs

I did consider that way when I did my post, and my conclusion is still that it should not be able be reached outside of the lan. I have the port mapped, so I can reach it outside of the reverse proxy, if that's not the case for you, doing a allow/deny is the next best option, outside of just disabling the admin panel in the container.

This is not a bug. The container has no idea what port you set on the host-side.

sounds like the database is missing, corrupted or set to read-only

Bitwarden_rs runs on port 80 by default, have you changed the app itself to listen to 8086? There is two ways you can tackle this. But which to choose depends on two things, do you use dns validation with swag, and do you have a internal dns server? If the answer to both is yes, you can just set up the local dns to point to swag on your subdomain. If it is no on either of those, you can use allow/deny in nginx to only let the lan subnet connect.

Follow the bitwarden_rs project. As stated in the post, i do not create these applications.

It is not implemented in this version.

The combability aspect is new for me. Yea, I plan on expanding the page in the near future

You cannot change ports when using the --network argument, it behaves similarly to host. you would have to use port 80.

And just to be sure, other sites on the same domain work?

This just enforces my suspicion of the app using a ip or something

And you are sure your app i set to connect to the subdomain?

Im not sure how advanced that feature is, like if it follows the html tag for favicon, or just assumes it lives on /favicon.ico, i have those errors too sometimes, and i havent seen anything bad from it.

Are you using the sample in swag?

Like the video. But my OCD really don't like the output, many of the fields are just not needed, I dedicated whole section on that on my write up on how to create a template.

It was. They have hid their changelog in a way that there is no reliable way to get notifications. They silently updated the requirements. Runs on latest build

Its been a while since i used HAProxy, but you need to set it to connect over https, but to not validate the cert, as it is self-signed

atleast give some config so we can help.

In what context are you using letsencypt in?

You are probably running into this browser resctriction: https://docs.organizr.app/books/troubleshooting/page/redirect-looping---samesite-errors

Might be worth mentioning somewhere that `https://github.com/<username>.png` works Pros: Easier Dynamic Prettier Cons:

Pretty sure you do that in the same variable > redis://username:password@[IP]:6379

Are you using macvlan?

As I noted in this PR. Expose is not the issue. https://github.com/Roxedus/docker-TS-DnsServer/pull/2#issuecomment-751127753