Anyone else getting a 500 error on backup attempt?

Version eidy-ui

For me, I don't get that Error 500:

Running versions appear the same as yours (I did reboot following each upgrade):

Edited Saturday at 02:11 PM5 days by GPritchard

This just started. Worked fine a couple of days ago. Did try a hard re-start, no effect.

Figured it out, if you disable PG3 in eisy-ui. backup will not work. If enable works.

Just now, EricBarish said:

Figured it out, if you disable PG3 in eisy-ui. backup will not work. If enable works.

Very interesting. Is this something that is really reproductible.

If so, replicate the error and check what error you are getting in the eisy-ui logs.

You can also open a ticket and send your log after replicating this error.

Yes it is reproductible. Here is the section with the error codes, looks like something to do with the plugins.

All plugs have been moved from PG3 and are now working, but not deleted in PG3.

this error with PG3 disabled on backup try.

---

2026-10-24 12:02:24 [error] web: Backup failed: Error: socket hang up

at AxiosError.from (/var/eisyui/node_modules/axios/dist/node/axios.cjs:874:24)

at RedirectableRequest.handleRequestError (/var/eisyui/node_modules/axios/dist/node/axios.cjs:3299:25)

at RedirectableRequest.emit (node:events:509:28)

at eventHandlers.<computed> (/var/eisyui/node_modules/follow-redirects/index.js:49:24)

at ClientRequest.emit (node:events:509:28)

at emitErrorEvent (node:_http_client:109:11)

at Socket.socketOnEnd (node:_http_client:617:5)

at Socket.emit (node:events:521:24)

at endReadableNT (node:internal/streams/readable:1735:12)

at process.processTicksAndRejections (node:internal/process/task_queues:90:21)

at Axios.request (/var/eisyui/node_modules/axios/dist/node/axios.cjs:4339:41)

at process.processTicksAndRejections (node:internal/process/task_queues:104:5)

at async eisyBackup (/var/eisyui/dist/server/services/system.js:600:33)

at async /var/eisyui/dist/server/routes/api/authenticated/system.js:86:18

2026-10-24 12:02:24 [error] web: Error with API request to GET /api/system/backup/create: socket hang up

eisy-logs-2026-10-24T16-04-30.zip

FYI - I got the same error with PG3 disabled. Re-enabled it and backup works.

@bmercier I got the backup 500 error after the most recent update yesterday.

Here;s my debug snippet:

2026-10-26 18:28:28 [debug] web: HTTP Request from ::ffff:192.168.0.108 - GET /api/plugins/store/local/list
2026-10-26 18:28:28 [info] web: Get local plugins
2026-10-26 18:28:28 [http] web: GET /api/plugins/store/local/list : 200 : 15ms
2026-10-26 18:28:31 [debug] web: HTTP Request from ::ffff:192.168.0.108 - GET /api/system/backup/create
2026-10-26 18:28:31 [info] web: Backing up zmatter
2026-10-26 18:28:31 [info] web: Checking if zmatter is connected
2026-10-26 18:28:31 [info] web: zmatter is connected
2026-10-26 18:28:31 [info] web: Backing up zmatter/ZWave
2026-10-26 18:28:31 [info] web: Backing up IoX
2026-10-26 18:28:31 [error] web: Backup failed: Error: socket hang up
at AxiosError.from (/var/eisyui/node_modules/axios/dist/node/axios.cjs:874:24)
at RedirectableRequest.handleRequestError (/var/eisyui/node_modules/axios/dist/node/axios.cjs:3299:25)
at RedirectableRequest.emit (node:events:509:28)
at eventHandlers.<computed> (/var/eisyui/node_modules/follow-redirects/index.js:49:24)
at ClientRequest.emit (node:events:509:28)
at emitErrorEvent (node:_http_client:109:11)
at Socket.socketOnEnd (node:_http_client:617:5)
at Socket.emit (node:events:521:24)
at endReadableNT (node:internal/streams/readable:1735:12)
at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
at Axios.request (/var/eisyui/node_modules/axios/dist/node/axios.cjs:4339:41)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async eisyBackup (/var/eisyui/dist/server/services/system.js:600:33)
at async /var/eisyui/dist/server/routes/api/authenticated/system.js:86:18
2026-10-26 18:28:31 [error] web: Error with API request to GET /api/system/backup/create: socket hang up
2026-10-26 18:28:31 [http] web: GET /api/system/backup/create : 500 : 259ms
2026-10-26 18:28:37 [debug] isy: Subscription vsid 0 had 63217 events for the last 100 hours and 58 minutes.
2026-10-26 18:28:44 [debug] web: Subscription vsid 1 had 203 events for the last 4 minutes.
2026-10-26 18:28:46 [debug] proxy: Proxy connection check: Successful.
2026-10-26 18:28:48 [debug] Polls: Sending short poll to plugin 1
2026-10-26 18:28:48 [info] Polls: Message sent to plugin (slot 1) successfully

A fix is coming.

For your understanding, the problem is a timing issue with the zmatter backup & IoX backup.

The zmatter backup creates a background process that creates & removes files in the IoX directory.

When PG3x is enabled, it is backed up between the zmatter & IoX backup. This gives time for the zmatter background process to complete.

When PG3x is disabled, the zwatter backup may not have completed when IoX backup starts.

So the fix will be this:

The backup process will no longer automatically trigger a zmatter backup. It will have to be done manually in the Protocols / ZWave section, before doing the system backup, just like it was in AC. There will be a clear dialog explaining that when starting a system backup.

eisy-ui 1.4.8 in beta has the fix. This should solve the backup issue.