SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Vaultwarden loads forever #498

New Issue
Closed
opened 2025-11-20 04:49:15 -05:00 by saavagebueno · 8 comments
saavagebueno commented 2025-11-20 04:49:15 -05:00
Owner
Copy Link

Originally created by @pflavio on GitHub (Feb 9, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Vaultwarden LXC

📂 What was the exact command used to execute the script?

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/vaultwarden.sh)"

📝 Provide a clear and concise description of the issue.

I created the LXC with 4 cores, 8 GB RAM and 8 GB disk space (to prevent this). The web interface just shows the logo in the top left and loads, but nothing ever happens. I've also updated to VaultWarden 1.33.1, Web-Vault to v2025.1.1 and set an Admin Token. I've trashed and recreated the LXC 3x now. Any idea what caused this?

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

🔄 Steps to reproduce the issue.

  1. create vm
  2. acces web UI at ip:8000

❌ Paste the full error output (if available).

🖼️ Additional context (optional).

No response

Originally created by @pflavio on GitHub (Feb 9, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Vaultwarden LXC ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/vaultwarden.sh)" ### 📝 Provide a clear and concise description of the issue. I created the LXC with 4 cores, 8 GB RAM and 8 GB disk space (to prevent [this](https://vaultwarden.discourse.group/t/vaultwarden-keeps-loading/2210)). The web interface just shows the logo in the top left and loads, but nothing ever happens. I've also updated to VaultWarden 1.33.1, Web-Vault to v2025.1.1 and set an Admin Token. I've trashed and recreated the LXC 3x now. Any idea what caused this? ### ⚙️ What settings are you using? - [ ] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 🔄 Steps to reproduce the issue. 1. create vm 2. acces web UI at ip:8000 ### ❌ Paste the full error output (if available). - ### 🖼️ Additional context (optional). _No response_
saavagebueno commented 2025-11-20 04:49:16 -05:00
Author
Owner
Copy Link

@pflavio commented on GitHub (Feb 9, 2025):

Should have read the description

@pflavio commented on GitHub (Feb 9, 2025): Should have read the description
saavagebueno commented 2025-11-20 04:49:16 -05:00
Author
Owner
Copy Link

@theparadox1083 commented on GitHub (Mar 2, 2025):

I've mirrored your own experience this morning finding very few resources, adjusting things, recreating the LXC, running with defaults. I even added a caddy entry to see if https would resolve the issue with no luck.

I feel like an idiot, but would you mind providing more context for the closing of this issue? I've looked around for a description somewhere that might shed some light on what I'm doing wrong but I've missed it.

Thank you.

@theparadox1083 commented on GitHub (Mar 2, 2025): I've mirrored your own experience this morning finding very few resources, adjusting things, recreating the LXC, running with defaults. I even added a caddy entry to see if https would resolve the issue with no luck. I feel like an idiot, but would you mind providing more context for the closing of this issue? I've looked around for a description somewhere that might shed some light on what I'm doing wrong but I've missed it. Thank you.
saavagebueno commented 2025-11-20 04:49:16 -05:00
Author
Owner
Copy Link

@uSlackr commented on GitHub (Apr 17, 2025):

This part: "Vaultwarden needs to be behind a proxy (Nginx Proxy Manager) to obtain HTTPS and to allow clients to connect."

@uSlackr commented on GitHub (Apr 17, 2025): This part: "Vaultwarden needs to be behind a proxy (Nginx Proxy Manager) to obtain HTTPS and to allow clients to connect."
saavagebueno commented 2025-11-20 04:49:16 -05:00
Author
Owner
Copy Link

@pflavio commented on GitHub (Apr 17, 2025):

I've mirrored your own experience this morning finding very few resources, adjusting things, recreating the LXC, running with defaults. I even added a caddy entry to see if https would resolve the issue with no luck.

I feel like an idiot, but would you mind providing more context for the closing of this issue? I've looked around for a description somewhere that might shed some light on what I'm doing wrong but I've missed it.

Thank you.

Sorry @theparadox1083 didn't see your comment back then, would have replied with what @uSlackr said. I didn't mean to ignore it! :)

@pflavio commented on GitHub (Apr 17, 2025): > I've mirrored your own experience this morning finding very few resources, adjusting things, recreating the LXC, running with defaults. I even added a caddy entry to see if https would resolve the issue with no luck. > > I feel like an idiot, but would you mind providing more context for the closing of this issue? I've looked around for a description somewhere that might shed some light on what I'm doing wrong but I've missed it. > > Thank you. Sorry @theparadox1083 didn't see your comment back then, would have replied with what @uSlackr said. I didn't mean to ignore it! :)
saavagebueno commented 2025-11-20 04:49:17 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Apr 17, 2025):

@theparadox1083

Image

We put it red so you can read it, yet you don't...

@tremor021 commented on GitHub (Apr 17, 2025): @theparadox1083 ![Image](https://github.com/user-attachments/assets/69c5b809-a7be-4f5c-a240-f7d55a576f11) We put it red so you can read it, yet you don't...
saavagebueno commented 2025-11-20 04:49:17 -05:00
Author
Owner
Copy Link

@uSlackr commented on GitHub (Apr 17, 2025):

This isn't clear. One could read it and not digest it. We could save a lot of questions if we add "If you try to open the web page directly on the new container, the web site will not load".

@uSlackr commented on GitHub (Apr 17, 2025): This isn't clear. One could read it and not digest it. We could save a lot of questions if we add "If you try to open the web page directly on the new container, the web site will not load".
saavagebueno commented 2025-11-20 04:49:17 -05:00
Author
Owner
Copy Link

@theparadox1083 commented on GitHub (Apr 17, 2025):

@uSlackr Thanks! I did see that but from other sources I thought lack of HTTPS wouldn't prevent any interaction at all, just the limited access I will mention later.

@tremor021 I don't appreciate you assuming the worst of me. In my attempt to find out what I did wrong, I found a step by step video and they didn't need HTTPS to load the page. I remember that they confirmed it was up and before they set it up with HTTPS, then logged in over HTTPS. Over a dozen responses were having the same problem as me unable to load the page at that point so I kept searching until I found this issue.

@theparadox1083

Image
We put it red so you can read it, yet you don't...

I'm using Caddy instead of NPM, which I meantioned, to get HTTPS. It didn't resolve the issue, at least not right away. That's why I stated:

I even added a caddy entry to see if https would resolve the issue with no luck.

In my mind, I tried HTTPS, and it didn't work... so I assumed there was something else I missed.

My organization started using Vaultwarden where I work, though I was not at all involved in the setup process. With that installation we are not yet using HTTPS. Access is internal only and even then only accessible to whitelisted IPs for security. We suffer some loss of functionality with the Bitwarden browser extension and phone app but the site is still accessible. I was, apparently incorrectly, assuming that the warning was that I should expect limited functionality without HTTPS. Obviously, using it on a public-facing server without HTTPS would also be an insanely bad idea. I didn't expect the page to be unreachable without HTTPS. With this, the video, and this issue I was quite flummoxed.

Admittedly, I'm new to Caddy, so maybe I did something wrong. I'm only using basic reverse proxy and cloudflare tls.

Eventually I got it working. If I remember correctly, I think I just forgot to shut down the LXC or rebooted the node and it was set to auto start (with the Caddy entry still providing HTTPS) and I tested it again later when I noticed it was running and everything just worked. Maybe I'll try to reproduce it again some time to see what went wrong or right.

@theparadox1083 commented on GitHub (Apr 17, 2025): @uSlackr Thanks! I did see that but from other sources I thought lack of HTTPS wouldn't prevent any interaction at all, just the limited access I will mention later. @tremor021 I don't appreciate you assuming the worst of me. In my attempt to find out what I did wrong, I found a step by step video and they didn't need HTTPS to load the page. I remember that they confirmed it was up and before they set it up with HTTPS, then logged in over HTTPS. Over a dozen responses were having the same problem as me unable to load the page at that point so I kept searching until I found this issue. > [@theparadox1083](https://github.com/theparadox1083) > > ![Image](https://github.com/user-attachments/assets/69c5b809-a7be-4f5c-a240-f7d55a576f11) > We put it red so you can read it, yet you don't... I'm using Caddy instead of NPM, which I meantioned, to get HTTPS. It didn't resolve the issue, at least not right away. That's why I stated: > I even added a caddy entry to see if https would resolve the issue with no luck. In my mind, I tried HTTPS, and it didn't work... so I assumed there was something else I missed. My organization started using Vaultwarden where I work, though I was not at all involved in the setup process. With that installation we are not yet using HTTPS. Access is internal only and even then only accessible to whitelisted IPs for security. _We suffer some loss of functionality with the Bitwarden browser extension and phone app but the site is still accessible._ I was, apparently incorrectly, assuming that the warning was that I should expect _limited_ functionality without HTTPS. Obviously, using it on a public-facing server without HTTPS would also be an insanely bad idea. I didn't expect the page to be unreachable without HTTPS. With this, the video, and this issue I was quite flummoxed. Admittedly, I'm new to Caddy, so maybe I did something wrong. I'm only using basic reverse proxy and cloudflare tls. Eventually I got it working. If I remember correctly, I think I just forgot to shut down the LXC or rebooted the node and it was set to auto start (with the Caddy entry still providing HTTPS) and I tested it again later when I noticed it was running and everything just worked. Maybe I'll try to reproduce it again some time to see what went wrong or right.
saavagebueno commented 2025-11-20 04:49:17 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Apr 18, 2025):

@uSlackr @theparadox1083

Ok, let me get this straight...

VW official page tells you you need HTTPS to access:
Image

Reddit tells you you need HTTPS to access:
Image

Your browser tells you the same:
Image

We tell you you need HTTPS:
Image

Somehow all this is unclear and you are confused? I'm genuinely in loss for words... Only thing you ever need for it to work is to put VW behind a proxy, we put NPM as a example, doesn't matter what proxy you use, its up to you. Thats it, just do as we said in BIG RED BOX on script webpage... Its there for a reason. Its not a free interpretation. DO AS IT SAYS!

About the big wall of text you wrote @theparadox1083 , i really didn't read any of it since you failed a basic step we asked you to do.
I really don't know what else to say...

@tremor021 commented on GitHub (Apr 18, 2025): @uSlackr @theparadox1083 Ok, let me get this straight... VW official page tells you you need HTTPS to access: ![Image](https://github.com/user-attachments/assets/8eaf68ff-544f-44cd-88af-c2d6c14cd288) Reddit tells you you need HTTPS to access: ![Image](https://github.com/user-attachments/assets/aae31c81-8b94-4018-aca5-d4278eb2cd59) Your browser tells you the same: ![Image](https://github.com/user-attachments/assets/74ee788c-1bb8-4f97-8cf9-1e7b6e88f282) We tell you you need HTTPS: ![Image](https://github.com/user-attachments/assets/7c4700b8-4e09-4a42-ab9c-61a998353d47) Somehow all this is unclear and you are confused? I'm genuinely in loss for words... Only thing you ever need for it to work is to put VW behind a proxy, we put NPM as a example, doesn't matter what proxy you use, its up to you. Thats it, just do as we said in BIG RED BOX on script webpage... Its there for a reason. Its not a free interpretation. DO AS IT SAYS! About the big wall of text you wrote @theparadox1083 , i really didn't read any of it since you failed a basic step we asked you to do. I really don't know what else to say...
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#498
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?