Roxedus

Community Developer
  • Content Count

    225
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Roxedus

  1. 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.
  2. This is not a bug. The container has no idea what port you set on the host-side.
  3. sounds like the database is missing, corrupted or set to read-only
  4. 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.
  5. Follow the bitwarden_rs project. As stated in the post, i do not create these applications.
  6. It is not implemented in this version.
  7. You cannot change ports when using the --network argument, it behaves similarly to host. you would have to use port 80.
  8. And just to be sure, other sites on the same domain work?
  9. This just enforces my suspicion of the app using a ip or something
  10. And you are sure your app i set to connect to the subdomain?
  11. 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.
  12. 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
  13. 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
  14. atleast give some config so we can help.
  15. In what context are you using letsencypt in?
  16. You are probably running into this browser resctriction: https://docs.organizr.app/books/troubleshooting/page/redirect-looping---samesite-errors
  17. Might be worth mentioning somewhere that `https://github.com/<username>.png` works Pros: Easier Dynamic Prettier Cons:
  18. Pretty sure you do that in the same variable > redis://username:password@[IP]:6379
  19. As I noted in this PR. Expose is not the issue. https://github.com/Roxedus/docker-TS-DnsServer/pull/2#issuecomment-751127753
  20. Did you actually enable the DHCP scope? it doesnt listen before there is a enabled DHCP scope.
  21. I seem to have lost drive temps on most of my drives, only my NVME is showing, neither my HDDs or SSDs show, unassigned or not.
  22. I have had success going back to /user on the latest RC. 3 days and counting