Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid Server when using vaultwarden (Flatpak Installated) #308

Open
unkwn1-repo opened this issue Dec 4, 2024 · 4 comments
Open

Invalid Server when using vaultwarden (Flatpak Installated) #308

unkwn1-repo opened this issue Dec 4, 2024 · 4 comments

Comments

@unkwn1-repo
Copy link

I have vaultwarden setup locally. Using Goldwarden cli installed via AUR I have no issues connecting to my server using the directions from the cli wiki - i.e:

vault.domain.lan/api
vault.domain.lan/notifications
vault.domain.lan/identity

For some reason I cannot use the same configuration with the flatpak. I've even tried editing the config file for the flatpak ~/.var/app/com.quexten.Goldwarden/goldwarden.json. It had the official bitwarden urls.

After that change, and restarting the flatpak app the default url in the login form is still the official bitwarden one and when I input my servers local address it still says its invalid.

The server has https, a fqdn and, lan servers have the CA that signed the SSLs trusted.

Not sure what to do, would love to use this with the GUI but, im losing my mind lol

Running endeavourOS - latest linux kernel.

@edmundo096
Copy link

I'm quite new to flatpak but I have a feel that you need to kill the actual background process from flatpak.

Get the process instance flatpak ps then input it on flatpak kill <instance id>, or just kill all of Goldenwarden instances with flatpak kill com.quexten.Goldwarden.

Then start it from the icon or command with flatpak run com.quexten.Goldwarden, and it should load the new config from ~/.var/app/com.quexten.Goldwarden/goldwarden.json

Hope it helps, otherwise I'm lost

@linesquarecube
Copy link

I am experiencing the same issue and cannot make any progress.

I have already tried the hints given in #190, as entering my server address in the GUI while trying to log in did not update the entries in the configuration file.

After manually setting the environment with

flatpak run --command=/app/bin/goldwarden com.quexten.Goldwarden config set-api-url https://my.local.vaultwarden/api
flatpak run --command=/app/bin/goldwarden com.quexten.Goldwarden config set-identity-url https://my.local.vaultwarden/identity
flatpak run --command=/app/bin/goldwarden com.quexten.Goldwarden config set-notifications-url https://my.local.vaultwarden/notifications

the output of flatpak run --command=/app/bin/goldwarden com.quexten.Goldwarden config get-environment now shows the addresses of my local Vaultwarden instance as expected.

However, logging in is still not possible due to the error: "Failed to set server The server you entered is invalid, please try again."

Grateful for any hints or advice 😃

@linesquarecube
Copy link

linesquarecube commented Feb 18, 2025

Unfortunately, the wiki only mentions setting the URLs for api, notifications and identity via CLI in the Setting up your vault & logging in section.

I stumbled on #320. One thing that jumped out at me is that you need to set the vault URL manually. Which, yeah, makes total sense now that I think about it 😉.

After also setting the vault URL itself with

flatpak run --command=/app/bin/goldwarden com.quexten.Goldwarden config set-vault-url https://my.local.vaultwarden

login via CLI and GUI are working.

The only problem I haven't figured out yet is that the entries keep overwriting themselves after a short while.

@abear1538
Copy link

This smells like an issue that needs fixing in the UI and not endless terminal hell workarounds.

In 2025 users should never have to touch the terminal to make your app work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants