Do you see the network request for when you click the button initially? It should have a path that includes “createOffsiteBackupSchedule”. Are you creating a new schedule or using an existing FMS schedule? Do you see anything in the otto-info.log file?
You can find the otto-info.log on the logs page in OttoFMS. You should be able to select it from the dropdown in the top left. I’m not sure it will have anything useful to us here but it might. You can also check the Event log for logs about whether an FMS schedule gets created when you run that.
For the “use existing” option we’re not doing much on the backend beyond updating a database. A clean OttoFMS install is probably not a bad idea, if the problem is with your database that would fix it.
There are no log records being created following this process. Seems like the front-end is not reaching the back-end if that makes sense. The FETCH calls I see in the network tab in the browser’s console are not completing (nor timing out).
I found 2 error entries that could be related, maybe they could be helpful:
2025-03-01T22:06:40.458Z info Reverse Proxy already installed
2025-03-01T22:06:40.583Z error Error checking installed license TypeError: fetch failed
2025-03-01T22:06:55.598Z error Error cleaning up offsite schedules Local Admin API error: fetch failed; Error: connect ECONNREFUSED 127.0.0.1:16001; Path: /fmi/admin/api/v2/user/auth
