

2·
21 hours agoThanks for sharing the other communities. I have used this forum a lot and there are some great helpers here. I really hope things don’t get a bad turn. We really need these forums to help newbies. We’ve all been there. You could argue that the typical newbie question “where do i start?” Is “low effort” but simply reading all the answers about how others approched self hosting has given me so much benefit.
I’m picking up on this because I’m getting a bit confused. I’ve run this through docker compose using the below yaml. I’ve done it as normal user, “Fred” (added to docker group) rather than root (using sudo although it make no difference as I get the same outcome). I normally have a “docker” folder in my /home/fred/ folder so is /home/fred/docker/vaultwarden in this instance (i.e. my data folder is in here).
I get the same issue highlighted here which is all about the SSL_ERROR_RX_RECORD_TOO_LONG when trying to connect via https, whereas when I try to connect via http, I get a white page with Vaultwarden logo in top left corner and the spinning wheel in the center. I’ve got no proxy enabled and I’m still not clear why I need one if I’m only accessing this via LAN. Is this something on the lines of “you must yse this through a proxy or it won’t work” thing? Although that not why I understood the from the guidance. I’m clearly missing something although not sure what exactly it is …
services: vaultwarden: image: vaultwarden/server:latest container_name: vaultwarden restart: always environment: # DOMAIN: "https://vw.home.home/" SIGNUPS_ALLOWED: "true" volumes: - ./vw-data/:/data/ ports: - 11001:80