Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrating from version 4.0.0 to version 5.0.2 #2669

Closed
7 of 8 tasks
bsquared938 opened this issue Jul 24, 2023 · 0 comments
Closed
7 of 8 tasks

Migrating from version 4.0.0 to version 5.0.2 #2669

bsquared938 opened this issue Jul 24, 2023 · 0 comments

Comments

@bsquared938
Copy link

Is there a pinned issue for this?

  • I have read the pinned issues and could not find my issue

Is there an existing or similar issue/discussion for this?

  • I have searched the existing issues
  • I have searched the existing discussions

Is there any comment in the documentation for this?

  • I have read the documentation, especially the FAQ and Troubleshooting parts

Is this related to a provider?

  • I have checked the provider repo for issues
  • My issue is NOT related to a provider

Are you using the latest release?

  • I am using the latest release

Have you tried using the dev branch latest?

  • I have tried using dev branch

Docker run config used

(this was done on a Synology NAS so I don't have a true docker compose file, providing screenshots)
transmissionSettings3
transmissionSettings5

Current Behavior

Container keeps restarting after a fatal error

Expected Behavior

Container should stay running

How have you tried to solve the problem?

  1. removed pointer to VPN credentials and instead pointed to /config directly
  2. removed credentials from webUI to see if that happened to be interfering

Log output

image

HW/SW Environment

- OS: 
- Docker:

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.

Repository owner locked and limited conversation to collaborators Jul 24, 2023
@pkishino pkishino converted this issue into discussion #2670 Jul 24, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant