Migrating from version 4.0.0 to version 5.0.2 #2670
Replies: 2 comments
-
Please read through the documentation and existing issues..this is NOT a container issue, it is a config problem on your end. |
Beta Was this translation helpful? Give feedback.
-
Went through the documentation and a lot of other issues on here -- seems there is a lot that changed between versions. Also the container image size is twice as big as version 4 (that alone should make it clear that a lot has changed). I have started the container up from scratch and am slowly adding all the functionality back to it that I had before. It is working as intended. For anyone who tries this: you will likely need to do the same when migrating from version 4 to 5. |
Beta Was this translation helpful? Give feedback.
-
Is there a pinned issue for this?
Is there an existing or similar issue/discussion for this?
Is there any comment in the documentation for this?
Is this related to a provider?
Are you using the latest release?
Have you tried using the dev branch latest?
Docker run config used
(this was done on a Synology NAS so I don't have a true docker compose file, providing screenshots)
Current Behavior
Container keeps restarting after a fatal error
Expected Behavior
Container should stay running
How have you tried to solve the problem?
Log output
HW/SW Environment
Anything else?
Things were working fine in version 4.0.0 but something has changed with config files in 5.0.2.
I even downloaded a new OpenVPN config file from my provider and it's identical to the one that I had. I suspect a path/volume issue is messing things up here.
Will keep trying after I post this issue.
Beta Was this translation helpful? Give feedback.
All reactions