Thanks for the reply.
Synology told me similar: install DSM on alternate disk or do a hard reset.
That i want to avoid at all cost as it would take me days or even longer to get it back to a decent system again.
They first asked me to send a log file (debug.dat). Did that.
From that they concluded i had some 3rd party packages (like minecraft server for my son) so that must be the problem (sigh).
All 3rd party package are not running for a while and nothing changed to that for months or even years.
They didnt even bother to look at the debug.dat better...
So i replied to pls check the debug.dat file and btw i found out some stuff in the mean time and explained.
They replied again seemingly not reading my arguments (feels like 3rd party support agency that do not know what they are talking about) and said, well you should try installen dsm on a seperate disk and see if it persists....
Reading your reply it seems their standard argument/remedy and it sounds like they know they screwed up something but do not want to make it public (as some updates fixed something for you).
My findings till now:
Nginx is definitely the default backend web server. It was running ok on apache 2.2 for me but a week back decided to give nginx a try as i was experimenting with websockets and wanted to see if security wise a different backend server would be different. Once you go nginx you never go back seems to be my problem. Since then my websites do (of-course) not work anymore. Trying to swicth back to apache 2.2 (as per option given in web station) gives an 'operation failed' in the DSM mgt UI.
Also after that my Synology is giving me a strange error message of not being able to start up correctly and telling me to contact support (which does not help...)
When on the command line executing: 'nginx -s reload' i get:
nginx: [emerg] BIO_new_file("/usr/local/etc/certificate/WebStation/vhost_0cc94188-78bc-4544-823c-72bf1deebe6e/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/usr/local/etc/certificate/WebStation/vhost_0cc94188-78bc-4544-823c-72bf1deebe6e/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file).
So that seems at least to be a problem that needs fixing. Giving synology support this message returns in the answer given (try to install DSM on alternate disk.) BTW asking how that works also is not answered...
Why cant they explain me how i fix this certificate error?
Which packages did you re-install? Can you be more specific on which and how pls? Want to see if it makes sense to do as well and see what that brings.
Thanks in advance for any support given.
BTW i found this for converting older .htacces towards nginx config file: https://winginx.com/en/htaccess
. Also seems to work for Auth things. (it seems...). Cant verify of-course yet...
If others are willing to help please feel free, would appreciate.
Can someone explain how the webserver setup now works on Synology? When you choose apache 2.2 is it then apache all the way? Or is only part apache and below somewhere still nginx?
By default all attempts to reach my web pages get redirected to the 5000 port. Guess that nginx does that. But making a config file (after a lot of googeling) and putting that in conf.d dir did not bring me anything. Or do i need to do more?
Perhaps because nginx does not really start all the way due to the missing certificate file?