Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Vaultwarden
  3. Cannot log in after updating the app

Cannot log in after updating the app

Scheduled Pinned Locked Moved Solved Vaultwarden
9 Posts 3 Posters 1.1k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • archosA Offline
      archosA Offline
      archos
      wrote on last edited by archos
      #1

      Hi, after updating the Vaultwarden app, I can't log into the web interface. The page is showing me this error.
      Service Unavailable
      The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

      Apache/2.4.52 (Ubuntu) Server at my domain Port 8000

      I already had a problem with this last update and addressed it with your support and now it seems to be the same bug. Thank you very much for your help.

      girishG 1 Reply Last reply
      0
      • archosA archos

        Hi, after updating the Vaultwarden app, I can't log into the web interface. The page is showing me this error.
        Service Unavailable
        The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

        Apache/2.4.52 (Ubuntu) Server at my domain Port 8000

        I already had a problem with this last update and addressed it with your support and now it seems to be the same bug. Thank you very much for your help.

        girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #2

        @archos Does rolling back to previous version make it work? Can you also check the mysql logs? Is MySQL crashing again?

        archosA 1 Reply Last reply
        0
        • girishG girish

          @archos Does rolling back to previous version make it work? Can you also check the mysql logs? Is MySQL crashing again?

          archosA Offline
          archosA Offline
          archos
          wrote on last edited by
          #3

          @girish Thank you for your reply. Reverting to the previous version works. I can't find the MySQL log.

          girishG 1 Reply Last reply
          0
          • archosA archos

            @girish Thank you for your reply. Reverting to the previous version works. I can't find the MySQL log.

            girishG Offline
            girishG Offline
            girish
            Staff
            wrote on last edited by
            #4

            @archos Can you lock the automatic update for the moment for the app and post your cat /proc/cpuinfo ? So far, we pushed the new update to many new servers with no issue.

            archosA 2 Replies Last reply
            0
            • girishG girish

              @archos Can you lock the automatic update for the moment for the app and post your cat /proc/cpuinfo ? So far, we pushed the new update to many new servers with no issue.

              archosA Offline
              archosA Offline
              archos
              wrote on last edited by archos
              #5

              @girish I stopped the automatic update. Here is a printout from cat /proc/cpuinfo
              And from the terminal via ssh is here, but it's probably the same

              1 Reply Last reply
              0
              • girishG girish

                @archos Can you lock the automatic update for the moment for the app and post your cat /proc/cpuinfo ? So far, we pushed the new update to many new servers with no issue.

                archosA Offline
                archosA Offline
                archos
                wrote on last edited by
                #6

                @girish Would you please have any advice so I can update the app?

                1 Reply Last reply
                0
                • archosA Offline
                  archosA Offline
                  archos
                  wrote on last edited by
                  #7

                  I tried updating the app manually and the log said this
                  I hope I did everything right, but I think the problem was with a badly set YUBICO_SERVER
                  I set the Yubico server to False in the config.json file and so far everything seems to be fine. I think we can call this thread resolved.

                  robiR 1 Reply Last reply
                  2
                  • archosA archos

                    I tried updating the app manually and the log said this
                    I hope I did everything right, but I think the problem was with a badly set YUBICO_SERVER
                    I set the Yubico server to False in the config.json file and so far everything seems to be fine. I think we can call this thread resolved.

                    robiR Offline
                    robiR Offline
                    robi
                    wrote on last edited by
                    #8

                    @archos great, mark it so from the gear icon, first as a question, then as solved.

                    Conscious tech

                    1 Reply Last reply
                    2
                    • archosA archos marked this topic as a question on
                    • archosA archos has marked this topic as solved on
                    • girishG Offline
                      girishG Offline
                      girish
                      Staff
                      wrote on last edited by
                      #9

                      To keep the post complete, the logs is as below:

                      
                      
                      2023-04-29 16:42:36,348 INFO exited: core (exit status 12; not expected)
                      Apr 29 18:42:36 Error loading config:
                      Apr 29 18:42:36 [WARNING] Please use the admin panel to make changes to them:
                      Apr 29 18:42:36 [WARNING] SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, YUBICO_CLIENT_ID, YUBICO_SECRET_KEY
                      Apr 29 18:42:36 [WARNING] The following environment variables are being overriden by the config.json file.
                      Apr 29 18:42:36 `YUBICO_SERVER` must be a valid URL and start with 'https://'. Either unset this variable or provide a valid URL.
                      Apr 29 18:42:39
                      Apr 29 18:42:39
                      Apr 29 18:42:39
                      Apr 29 18:42:39
                      Apr 29 18:42:39 /--------------------------------------------------------------------\
                      Apr 29 18:42:39 2023-04-29 16:42:39,355 INFO spawned: 'core' with pid 104
                      Apr 29 18:42:39 2023-04-29 16:42:39,378 INFO exited: core (exit status 12; not expected)
                      Apr 29 18:42:39 Error loading config:
                      Apr 29 18:42:39 [INFO] Using saved config from `/app/data/config.json` for configuration.
                      Apr 29 18:42:39 [WARNING] Please use the admin panel to make changes to them:
                      Apr 29 18:42:39 [WARNING] SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, YUBICO_CLIENT_ID, YUBICO_SECRET_KEY
                      Apr 29 18:42:39 [WARNING] The following environment variables are being overriden by the config.json file.
                      Apr 29 18:42:39 \--------------------------------------------------------------------/
                      Apr 29 18:42:39 `YUBICO_SERVER` must be a valid URL and start with 'https://'. Either unset this variable or provide a valid URL.
                      Apr 29 18:42:39 | Starting Vaultwarden |
                      Apr 29 18:42:39 | https://github.com/dani-garcia/vaultwarden/discussions or |
                      Apr 29 18:42:39 | https://github.com/dani-garcia/vaultwarden/issues/new |
                      Apr 29 18:42:39 | https://vaultwarden.discourse.group/ |
                      Apr 29 18:42:39 | Report suspected bugs/issues in the software itself at: |
                      Apr 29 18:42:39 | Send usage/configuration questions or feature requests to: |
                      Apr 29 18:42:39 | This is an *unofficial* Bitwarden implementation, DO NOT use the |
                      Apr 29 18:42:39 | official channels to report bugs/features, regardless of client. |
                      
                      1 Reply Last reply
                      1
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                        • Login

                        • Don't have an account? Register

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • Bookmarks
                        • Search