SYNERGY
Chapters

2.7Troubleshooting installation

Last updated

SymptomLikely cause and remedy
The installer refuses to start, naming the ASP.NET Core ModuleInstall the ASP.NET Core 10 Hosting Bundle (after IIS), then run the installer again.
Every page answers HTTP 500.19 or 500.31The Hosting Bundle is missing or was installed before IIS. Repair the Hosting Bundle.
The readiness check fails at the end of setupThe application pool identity has no rights on the database, the database does not exist, or a kill switch entry matches no operation. Read C:\Logs\startup-*.log and the application log.
The readiness check fails although the site works in a browser elsewhereThe server cannot resolve or reach its own public base URL (for example, the name only resolves outside the network). Make the name resolve on the server, or check the readiness address by hand.
The readiness check fails and Apply migrations at startup is offExpected: bring the database up to date with your own process, then restart the application pool.
Nobody can sign in; the sign-in page returns to itselfThe site is reached over HTTP, or Auth cookie Secure is off while SameSite is None. Use HTTPS.
The console loads but every action failsThe address in the browser is not listed in Allowed origins. Run the wizard again and add it.
All users share one rate limitA reverse proxy sits in front of IIS but is not listed under Known proxies or Known networks.
The first-run page says setup must be completed on the serverOpen the site from a browser on the server itself.
Saved directory connections stopped working after reconfiguringThe credential encryption key was changed. Restore the previous value, or re-enter the connection passwords.
The Windows sign-in button does not appearWindows sign-in was not configured in IIS (Windows sign-in set to On), is not enabled in the console, or the sso module is not licensed. See Chapter 17, Single sign-on.

If setup did not complete, nothing needs to be undone before you run it again: every step can be repeated, and the previous configuration file was backed up.

Last updated

Did this page help you?