topic Re: Post WebGIS DR restore error: Invalid Token for federated server in High Availability and Disaster Recovery Questions

Post WebGIS DR restore error: Invalid Token for federated server

WarrenMedernach — Tue, 22 Jun 2021 16:25:07 GMT

Current environment:

2 servers at 10.8.1, both running Windows Server 2016:
- 1 primary hosting server running Portal, Server and webadaptors
- 1 image server

I've completed a WebGIS DR restore to a new machine for our primary hosting server, and now when I try to federate the second server (Image Server) it is returning and error when it validates:

Error: The server at 'https://<FQDN of image server>:6443/arcgis/admin/info' returned and error. Server machine 'https://<FQDN of hosting server>:7443/arcgis/sharing/rest/community/self' returned an error. 'Invalid Token'.

Any ideas where to dig into this?

Re: Post WebGIS DR restore error: Invalid Token for federated server

NicolasGIS — Sun, 16 Jun 2024 07:32:02 GMT

Hello @WarrenMedernach,

facing a similar issue when going through LB after webgisdr restore as well: did you ever find what was the issue ?

thanks !

Re: Post WebGIS DR restore error: Invalid Token for federated server

rshihab — Tue, 02 Jul 2024 18:54:31 GMT

Hi,

Did you check the configuration of the LB it should allow the request if the internal machine name then traverse back with the hostname (webcontext URL) , is the SSL attached at the LB Level

Re: Post WebGIS DR restore error: Invalid Token for federated server

NikoR — Thu, 13 Nov 2025 03:46:23 GMT

Sorry to resurrect an old post, but did you ever get this to work? I'm experiencing the same issue.

Re: Post WebGIS DR restore error: Invalid Token for federated server

WarrenMedernach — Fri, 14 Nov 2025 14:55:35 GMT

Hi @NikoR , I'm really sorry, but I cannot recall exactly how we resolved this. It might have been a certificate issue, but I can't say for sure.

Re: Post WebGIS DR restore error: Invalid Token for federated server

SimonSchütte_ct — Tue, 02 Dec 2025 14:33:15 GMT

Check if your credentials align. I had similar issues after password changes and restores. parts of the deployments still had the old credentials and therefore could not generate the token.
Checking certificates is also a good tip.