XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Google Sign-in stopped working "internal server error" (log attached)

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    12 Posts 3 Posters 718 Views 3 Watching
    Loading More Posts
    • 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.
    • S Offline
      sluflyer06
      last edited by olivierlambert

      Not sure what is going on, I've been using Google oauth to sign into XO for a couple weeks and now it suddenly stopped working and I haven't changed anything with the plugin settings or on google cloud. It's the only plug-in I have installed, I also use google SSO on some other applications on another VM and they all seem to be fine (KASM, portainer, etc)

      InternalOAuthError: Failed to obtain access token
at Strategy.OAuth2Strategy._createOAuthError (/home/anthony/xen-orchestra/node_modules/passport-oauth2/lib/strategy.js:423:17)
at /home/anthony/xen-orchestra/node_modules/passport-oauth2/lib/strategy.js:177:45
at /home/anthony/xen-orchestra/node_modules/oauth/lib/oauth2.js:191:18
at ClientRequest.<anonymous> (/home/anthony/xen-orchestra/node_modules/oauth/lib/oauth2.js:162:5)
at ClientRequest.emit (node:events:513:28)
at ClientRequest.patchedEmit [as emit] (/home/anthony/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
at TLSSocket.socketErrorListener (node:_http_client:502:9)
at TLSSocket.emit (node:events:513:28)
at TLSSocket.patchedEmit [as emit] (/home/anthony/xen-orchestra/@xen-orchestra/log/configure.js:52:17)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at processTicksAndRejections (node:internal/process/task_queues:82:21)
      1 Reply Last reply Reply Quote 0
      • S Offline
        sluflyer06
        last edited by sluflyer06

        Shows my lack of Linux fu, the solution was flushing the default route in debian and then setting it to eth0.

        Edit(2 hours later): ended up being so much more digging to make that a persistent change, but appears to be working after reboot now.

        1 Reply Last reply Reply Quote 0
        • olivierlambertO Offline
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by

          Hi,

          It's hard to assist without knowing at all what XO are you using (XOA or XO from the sources) and if you did any update recently.

          S 1 Reply Last reply Reply Quote 0
          • S Offline
            sluflyer06 @olivierlambert
            last edited by

            @olivierlambert

            I'm running from sources. I recently switched from master to florents test branch for NBD stuff and back to master.

            commit 76bd5

            1 Reply Last reply Reply Quote 0
            • olivierlambertO Offline
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by

              This issue doesn't ring any bell to me. If you can cross check with an XOA fully up to date on latest branch, that might be helpful to find the problem.

              S 1 Reply Last reply Reply Quote 0
              • S Offline
                sluflyer06 @olivierlambert
                last edited by sluflyer06

                @olivierlambert So..the problem is I'm trying to add 2nd network to the XO VM that is attached to a 2nd PIF on the host to have a dedicated wire for backups. The backing up over that network works fine to the NAS(different physical box). But then the XO VM apparently decided to use eth1 for all it's web access instead of eth0 and therefore Google sign-in dies and you can't even ping google.com from debian terminal either.

                I'm not sure the right way to fix that, my standard subnet is 10.10.10.0 and I use .5.0 and .4.0 for storage networks, each box had 3x10Gb lines run to it

                1 Reply Last reply Reply Quote 0
                • S Offline
                  sluflyer06
                  last edited by sluflyer06

                  Shows my lack of Linux fu, the solution was flushing the default route in debian and then setting it to eth0.

                  Edit(2 hours later): ended up being so much more digging to make that a persistent change, but appears to be working after reboot now.

                  1 Reply Last reply Reply Quote 0
                  • olivierlambertO Offline
                    olivierlambert Vates 🪐 Co-Founder CEO
                    last edited by

                    Ah good catch then 🙂 Problem solved, right?

                    S 1 Reply Last reply Reply Quote 0
                    • S Offline
                      sluflyer06 @olivierlambert
                      last edited by

                      @olivierlambert there no XO problem. I thought I figured out how to have a 2nd network on the debian XO VM but I'm at a loss. I spent half the night trying to figure out how to make a persistent default gateway in debian and nothing seems to work. Either the VM has no access on my first subnet or ONLY has access to the 2nd subnet if I did a defined route in interfaces file. This seems like such a simple thing but I've tried everything from every forum I can find.

                      1 Reply Last reply Reply Quote 0
                      • olivierlambertO Offline
                        olivierlambert Vates 🪐 Co-Founder CEO
                        last edited by

                        Maybe because you tried to have 2 different default gateways? Which isn't possible. Anyway, thanks for the feedback, happy to know you found a solution 🙂

                        S 1 Reply Last reply Reply Quote 0
                        • olivierlambertO olivierlambert marked this topic as a question on
                        • olivierlambertO olivierlambert has marked this topic as solved on
                        • S Offline
                          sluflyer06 @olivierlambert
                          last edited by

                          @olivierlambert well I still can't have 2 networks in that VM, literally all I need to do is be able to set 10.10.10.1 in eth0 as the default gateway and I can find no way to do that. Debian is defaulting to eth1 with the backup network as default. I can find no persistent way to set a default gateway of my choosing.

                          H 1 Reply Last reply Reply Quote 0
                          • H Offline
                            HeMaN @sluflyer06
                            last edited by

                            @sluflyer06 if you use it like i do(*), just put a static ip and subnetmask on the storage network adapter and no gateway.

                            Only put a gateway in the internet connected adapters' network settings

                            (*) i have a separate vlan for storage with only static ip adresses assigned for that vlan on my hosts and nas, no internet connection, not even dns there.

                            S 1 Reply Last reply Reply Quote 0
                            • S Offline
                              sluflyer06 @HeMaN
                              last edited by sluflyer06

                              @HeMaN this may have actually worked...
                              In etc/network/interfaces

                              The primary network interface

                              allow-hotplug eth0
                              iface eth0 inet dhcp

                              This is an autoconfigured IPv6 interface

                              iface eth0 inet6 auto
                              post-up route add default via 10.10.10.1 dev eth0

                              auto eth1
                              iface eth1 inet static
                              address 10.10.5.188
                              post-up route del default dev eth1

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post