Roxedus

Community Developer
 View Profile  See their activity

  • Content Count

    213

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Everything posted by Roxedus

  1. Roxedus
    This was the missing part. We do indeed recommend that.
  2. Roxedus
    Define this
  3. Roxedus
    Looks like its time to close my feature request now.
  4. Roxedus
    the admin panel needs another regex to catch failed attempts
  5. Roxedus
    Just checked the wiki
  6. Roxedus
    And singup is disallowed in the admin panel?
  7. Roxedus
    I just use CA backup, then rclone that archive to the cloud.
  8. Roxedus
    If you are using swag, use the sample in swag.
  9. Roxedus
    I didnt touch anything, if anything changed it had to be technium pushing a update thats not in the changelog, or that one of the few dependencies broke something.
  10. Roxedus
    It all boils down to security. For the webpage, it is a limitation set by the browser. And for the apps, Its a decision by bitwarden.
  11. Roxedus
    It really should work if you map the port.
  12. 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)
  13. Roxedus
    If it is anything like the iOS app, if keeps its own chain of certs
  14. Roxedus
    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.
  15. Roxedus
    This is not a bug. The container has no idea what port you set on the host-side.
  16. Roxedus
    sounds like the database is missing, corrupted or set to read-only
  17. Roxedus
    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.
  18. Roxedus
    Follow the bitwarden_rs project. As stated in the post, i do not create these applications.
  19. Roxedus
    It is not implemented in this version.
  20. Roxedus
    You cannot change ports when using the --network argument, it behaves similarly to host. you would have to use port 80.
  21. Roxedus
    And just to be sure, other sites on the same domain work?
  22. Roxedus
    This just enforces my suspicion of the app using a ip or something
  23. Roxedus
    And you are sure your app i set to connect to the subdomain?
  24. Roxedus
    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.
  25. Roxedus
    Are you using the sample in swag?