I have installed .net 9 on a windows 2019 datacentre VM.
I can get .net 9 apps running on this server, however, no such luck with U15.
So, a blank U15 site from latest Umbraco VS 2022 template. All runs fine in IISExpress.
It generates startup logs in /umbraco/logs, however any URL throws a 500, including to backoffice (/umbraco).
Problem is I cannot get any information on this 500. Nothing in /umbraco/logs, an empty stdout/log file, nothing in event viewer application logs.
Running from cmd with dotnet mydll.dll appears to start correctly, with no errors.
Only clue I can find is that the server never registers in DB umbracoServer table, and even entering a fake connection string to non-existing db - still see same apparent succesful startup behaviour and no descriptive logs.
Have published in debug mode with developer exception page enabled, set all logs to info level. I can see the request log in umbracoLog, just notes that it's a 500 response code but no stack trace.
Server is fully up to date, multiple restarts, but this behaviour persists.
Have spun up multiple IIS sites and created umbraco projects from scratch multiple times but have the same behaviour across all of them :(
I think I missed the log that said "Runtime mode validation failed for Production:\nUmbraco application URL needs to be set in production mode" as I dismissed it as a warning rather than an actual error that would prevent startup...
And for my SQL - well, haha, turned out I'd just not granted my SQL user permission to my db ¯_(ツ)_/¯
Setting runtime mode to development and enabling both the debug flags dumped the actual stack trace of the error out into the logs.
U15 on IIS10
Has anyone had any luck running U15 on IIS10?
I have installed .net 9 on a windows 2019 datacentre VM.
I can get .net 9 apps running on this server, however, no such luck with U15.
So, a blank U15 site from latest Umbraco VS 2022 template. All runs fine in IISExpress.
It generates startup logs in /umbraco/logs, however any URL throws a 500, including to backoffice (/umbraco).
Problem is I cannot get any information on this 500. Nothing in /umbraco/logs, an empty stdout/log file, nothing in event viewer application logs.
Running from cmd with dotnet mydll.dll appears to start correctly, with no errors.
Only clue I can find is that the server never registers in DB umbracoServer table, and even entering a fake connection string to non-existing db - still see same apparent succesful startup behaviour and no descriptive logs.
Have published in debug mode with developer exception page enabled, set all logs to info level. I can see the request log in umbracoLog, just notes that it's a 500 response code but no stack trace.
Server is fully up to date, multiple restarts, but this behaviour persists.
Have spun up multiple IIS sites and created umbraco projects from scratch multiple times but have the same behaviour across all of them :(
Has anyone else had any success with this setup?
I think I missed the log that said "Runtime mode validation failed for Production:\nUmbraco application URL needs to be set in production mode" as I dismissed it as a warning rather than an actual error that would prevent startup...
And for my SQL - well, haha, turned out I'd just not granted my SQL user permission to my db ¯_(ツ)_/¯
Setting runtime mode to development and enabling both the debug flags dumped the actual stack trace of the error out into the logs.
is working on a reply...