Well, that was harder than I thought. I was tired of waiting for Synology to update the WordPress version to the current one and started this little project to install the public version of WordPress on my Synology NAS and to migrate my website to that. Couldn’t be too difficult I thought. But it turned out that there were quite some obstacles to overcome; but finally, I succeeded, and I want to share my experiences with you.
As quite a lot of people have noticed already (e.g. here) the Synology Drive Client 3.2.0 – 13258 Update has a problem. After the update it is crashing silently all the time on my Macs. The advice from the Synology support to re-install the Drive client from scratch may be constructive but is quite tedious if you have a lot of shares configured (as for me). A hint in the above mentioned forum lead to the solution.
Obviously the password of the stored connection to the Synology NAS is corrupt after the update. Since the Drive client crashes very soon after startup the best procedure to restore the correct password is the following:
Well, for quite a while accessing reminders stored on my Synology NAS from my Mac was broken. Syncing with my iOS devices was no problem but on my Mac I could not see the folders and reminder items. Looking around in the internet showed that it was apparently problem since macOS 10.15. It seems that the Reminders client on the Mac does not accept the LetsEncrypt certificate on the Synology NAS.
Good news: With macOS 13 (Ventura) the sync is back on the Mac. No problems anymore neither on my Intel Mac nor on my Apple Silicon Mac.
Recently, I have updated my Synology NAS to DSM 7. I was positively surprised that most of the apps I use work without problems. The new Synology Photos app is not that nice compared to the old Photo Station 6 but anyway, it will improve, I hope.
There is a bigger update on the WebStation under DSM 7. Formerly, it was quite difficult to run a website (let’s say: a WordPress instance) under the main domain name of your installation (e.g. as
fpposchmann.de). The standard installation would access a WordPress instance under
fpposchmann.de/wordpress; quite ugly. The Apache aliases could not be configured in the WebStation. I found no way to change that by standard configuration means and ended up configuring my own