cheesemarathon

Ok so the issue must exist somewhere between Ghost and MySQL. I would enable the general query log on your MySQL container, which should show logs when Ghost attempts to connect. It might shed some more light on the situation.

Had a look through the logs and nothing jumps out at me. Only thing is that the errors are all at the same sort of time: 01:17, 02:17, 06:17, 07:16, 21:26, 22:26, 23:26 which leads me to think, something is happening on a regular interval to cause this issue. When you say you reinstalled the containers, did you delete the appdata directories for the containers as well, as any misconfiguration in there will just be carried over into the reinstall if not removed. The other thing I would check is, when you have the error, check to see if you can connect to MySQL from another service. Id install the Adminer container on UnRAID and something like DBeaver on another machine and test both.

Sorry having some issues with my server right now. Hopefully backup by Monday. In the meantime the way back archive has a copy: https://web.archive.org/web/20231227043755/https://squishedmooo.com/

Head to {your blog domain}/ghost and the UI should guide you through the setup

Thanks for the update and fix. I had spotted the issue myself but had not had time to look into a fix!

Cool I think I understand what is going on here. My first suggestion would be to not install MySQL. MariaDB is an opensource implementation of MySQL, so 99% of the time any application that can connect and use a MySQL database can also use a MariaDB database. So what I would do is set Ghost to use your MariaDB instance. Setup is the same. I'll put a screenshot of my config below for reference. Database IP is the IP address of the machine running MariaDB. I assume your unRAID machine. So something like 192.168.1.45 or whatever your IP scheme is. Database user and password are self explanatory. Database name is the name of the database within MariaDB you wish Ghost to use. The other issue you seem to be having is with the URL setting. If you are running a blog that can not be accessed from a domain name then leave it blank. If that fails then I would remove the variable entirely. Just click the remove button on the right hand side. If you ever plan to open your Ghost blog up to the internet, you will need to set this to the domain name your site will be reachable from. In my case it is `https://squishedmooo.com/` Note that as the error suggests, you need to include a protocol in the URL. https is correct for the most part. I hope that helps, but if you have any more questions, just shout.

I have had a further play with Minio and I have not been able to get it to run at all now. With the way Minio is being developed, it looks like they are tailoring it to be run on dedicated machines. As such I would not recommend you use it. I did find the last 100% working version somewhere in this thread which you could use if you wish but you wont get any updates. Sorry I couldn't be of more help. If you want to have a play with Minio more then I can give you a few theoretical answers. Mounting a specific disk `/mnt/disk1` for example to the `/data` directory should allow it to work. In theory you could mount `/mnt/disk1` to `/disk-1` and `/mnt/disk2` to `/disk-2` etc. You also need to set the environment variable `MINIO_VOLUMES="/data-{1...4}"` I believe another user had a play trying to get this work but did not succeed but in theory it should work. Docs on this type of setup are here. Also, with all the above minio is mounted to the root of the drives. Minio then could wipe all the data on that drive, so I'd mount it into a minio directory on each drive. I have no experience with a V-Disk at all, but again you should be able to get it to work similarly to how I have just described but with a V-Disk instead of a physical one. Speed would be very dependant on your system specs.

If I’m honest i don’t have answers to all your questions right now. I’ll spin up an instance of minio and have a play over the next couple of days and see what I can recommend!

OK so in the docker screen, tick the switch in the uptime column to enable auto start. Unraid will start the containers in the order they are on the screen. Make sure your database starts before ghost or it will fail to start.

Yes those are all my templates. You mentioned you couldn't get one to autostart. Which one could you not get to start. You have none of the templates in your screenshot installed.

Which constrainer are you referring to. This thread is for support of all the containers I have written an unRAID template for.

appologies that I didn’t get chance to message you the commands! Glad you worked it out though 😊

I haven't created any templates for unRAID for any other S3 storage services. I don't believe there are any in community applications. This is the best collection of potential alternatives that may work with unRAID but would need further investigation:

No it's the data directory that is the problem. This post explains the issue. RELEASE.2022-10-24T18-35-07Z is the last known working version without work arounds. I saw you added a message to the container in CA. Can you add that version tag to the message? Also how do you see these messages so quick @Squid 😛 do you have an alert on any mention of community applications? 😂

Good shout! I’ll see what I can do