{"ArticleId":null,"Name":"Start-up and installation errors","Content":"\n\u003Cp\u003EProblems that appear when the application starts, or when it is first installed.\u003C/p\u003E\n\n\u003Ch2 id=\u0022installer-again\u0022\u003EThe installation page appears again\u003C/h2\u003E\n\u003Cp\u003EGrandNode shows the installer when it finds no database settings. The connection string is stored in \u003Ccode\u003EApp_Data/Settings.cfg\u003C/code\u003E, written by the wizard. If you redeployed the application without that file - a new container, a fresh folder - the installer appears. Restore \u003Ccode\u003ESettings.cfg\u003C/code\u003E instead of installing again over a live database - or, better in containers, pass the connection string as the environment variable \u003Ccode\u003EConnectionStrings__Mongodb\u003C/code\u003E, which takes precedence over the file. The same applies to \u003Ccode\u003EInstalledPlugins.cfg\u003C/code\u003E: if it is lost, the store starts without its plugins. See \u003Ca href=\u0022/getting-started-docker-kubernetes\u0022\u003ERunning in production: Docker and Kubernetes\u003C/a\u003E.\u003C/p\u003E\n\n\u003Ch2 id=\u0022db-version\u0022\u003E\u0022The database version is not supported in this software version\u0022\u003C/h2\u003E\n\u003Cp\u003EThe application checks that the database version stamp matches what it supports. On an upgrade, migrations update the stamp automatically when the application starts. You see this message when:\u003C/p\u003E\n\u003Cul\u003E\n\u003Cli\u003Ethe database is \u003Cstrong\u003Enewer\u003C/strong\u003E than the application - for example after rolling back the code without restoring the database;\u003C/li\u003E\n\u003Cli\u003Ethe upgrade migrations \u003Cstrong\u003Efailed\u003C/strong\u003E - check the log of the first start after the upgrade.\u003C/li\u003E\n\u003C/ul\u003E\n\u003Cp\u003ERun the GrandNode version that matches the database, or restore the database backup taken before the upgrade. Always back up before upgrading.\u003C/p\u003E\n\n\u003Ch2 id=\u0022mongo\u0022\u003EMongoDB connection errors\u003C/h2\u003E\n\u003Cul\u003E\n\u003Cli\u003ECheck the connection string in \u003Ccode\u003ESettings.cfg\u003C/code\u003E: host, port, database name, user, and \u003Ccode\u003EauthSource\u003C/code\u003E when the user is defined in another database.\u003C/li\u003E\n\u003Cli\u003EIn Docker, the host is the service name of the MongoDB container, not \u003Ccode\u003Elocalhost\u003C/code\u003E.\u003C/li\u003E\n\u003Cli\u003EFirewalls and MongoDB\u0027s \u003Ccode\u003EbindIp\u003C/code\u003E must allow the application server.\u003C/li\u003E\n\u003C/ul\u003E\n\n\u003Ch2 id=\u0022proxy\u0022\u003EWrong URLs or redirect loops behind a proxy\u003C/h2\u003E\n\u003Cp\u003EBehind a reverse proxy, load balancer or Kubernetes ingress that terminates HTTPS, the application sees plain HTTP. Links then use \u003Ccode\u003Ehttp://\u003C/code\u003E, or HTTPS redirects loop. Set \u003Ccode\u003ESecurity:UseForwardedHeaders\u003C/code\u003E to \u003Ccode\u003Etrue\u003C/code\u003E (the proxy must send \u003Ccode\u003EX-Forwarded-Proto\u003C/code\u003E and \u003Ccode\u003EX-Forwarded-For\u003C/code\u003E), or \u003Ccode\u003ESecurity:ForceUseHTTPS\u003C/code\u003E. The store URL in \u003Cstrong\u003EConfiguration \u2192 Stores\u003C/strong\u003E must be the public HTTPS address.\u003C/p\u003E\n\n\u003Ch2 id=\u0022slow-first\u0022\u003EThe first request is slow\u003C/h2\u003E\n\u003Cp\u003EAfter a start, the first requests load plugins, compile views and fill the cache. It is normal for them to take several seconds. A health-check or warm-up request after deployment hides this from customers.\u003C/p\u003E\n\n\u003Ch2 id=\u0022related\u0022\u003ERelated\u003C/h2\u003E\n\u003Cul\u003E\n\u003Cli\u003E\u003Ca href=\u0022/getting-started-upgrading\u0022\u003EUpgrading GrandNode\u003C/a\u003E\u003C/li\u003E\n\u003Cli\u003E\u003Ca href=\u0022/system-appsettings\u0022\u003EApplication settings (appsettings.json)\u003C/a\u003E\u003C/li\u003E\n\u003C/ul\u003E\n","ParentCategoryId":"6abe3a3b04b9d0a2009fec01","SeName":"troubleshooting-startup","MetaKeywords":null,"MetaDescription":"GrandNode start-up problems: the installer appears again, the database version is not supported, MongoDB connection errors, wrong URLs behind a proxy.","MetaTitle":null,"AllowComments":false,"Captcha":{"ReCaptchaChallengeField":null,"ReCaptchaResponseField":null,"ReCaptchaResponseValue":null,"ReCaptchaResponse":null},"RelatedArticles":[],"CategoryBreadcrumb":[{"Name":"Troubleshooting and FAQ","Description":null,"IsCurrent":false,"Children":null,"Parent":null,"SeName":"docs-troubleshooting","Id":"6abe3a3b04b9d0a2009fec01","UserFields":[]}],"AddNewComment":{"CommentText":null,"DisplayCaptcha":false,"Id":null,"UserFields":[]},"Comments":[],"Id":"6abe3a3b04b9d0a2009fec11","UserFields":[]}