I want to provide a follow-up and conclusion to this issue. I’m pleased to say it has been resolved, and I am back up and running without any loss of data. I’m less pleased to have to admit that I don’t know how. I don’t know what caused the problem, or what fixed it. Here’s a few things I tried.
- I had SABnzbd installed from a Community Package in Package Centre in the Synology NAS. I learned that this is hard-coded to use port 8080 and that this cannot be changed. I removed this package. This didn’t seem to help. I didn’t think it would help because the port 8080 that I was trying to use was inside the Passbolt docker container, so any changes to port 8080 outside the container, to my thinking, would be irrelevant. I restarted after uninstalling this package, and the problem persisted.
- I updated the Synology NAS software to 7.1.1-42962 Update 5. This required a restart. After this restart the Passbolt container started and ran without generating any errors.
- There were several re-starts in the above two steps. I may just have been that multiple re-starts were required.
- When Passbolt was up and running, it was not working properly on Google Chrome. Other browsers worked okay. After an overnight wait, Google started working again. I don’t think this is a Passbolt issue per-se, but something to do with Google security checks. My site pb.mydomain.com.au had been (incorrectly) flagged as a phishing site by google. This seems to have sorted itself out with no intervention from my part. It may be been related to Google picking up on the multiple error pages that had been generated while Passbolt was not working.
Thanks to all those who have contributed to this issue and tried to help me.