prtik
400 error while accessing service monitoring
@Siumauricio its urgent, i did maintenance on server 'apt update && apt upgrade' and did reboot on my two servers, but one server is now unable to login to dokploy, insteadof login screen im seeing 404 not found, but web app and other services are fine. How do i fix it?
28 replies
backup cron issue/bug
Hello @Podgorski sorry for delayed response, unfortunately i didn't find cause that time and due to limited access to dokploy support i couldn't able to open a proper ticket to inform it also, as @Siumauricio couldn't able to replicate this im suspecting it's a very very specific bug and happening in specific conditions only and for few instances.. So what i did back then, since i had backup i completely removed the service and created new one, that way the docker container from which un-controllable mysql dump was executing was stoped and i setup new backup. I hope this helps you any way...
14 replies
backup cron issue/bug
1. Create 2 mariadb databases
2. Setup backblaze bucket storage
3. Setup backup job on both db and define prefix path for 1st db - db/ and 2nd db - dev/ and add cron - */3 * * * [every 3 min]
4. check if db are backing up.
5. now delete any of the db's backup job
Hopefully you'll see that backup still runs every 3 min, unless you stop that database container!
14 replies