Lockie

> I also have been using PUID and PGID since I started using the container and I still have this issue.

Bumping this if that's okay as I'd still like to see a fix as Im sure would many others.

I think I'm also getting the same issue or atleast similar. I'm looking at the Docker logs for my container and I'm seeing no errors.

Could NAT issues cause problems like this one?

Hey yeah sorry. I'm on the following version: Node version: mainnet (1.2.3-2e737829) NodeUI version: 1.7.0 I've tried updating my container (https://registry.hub.docker.com/r/mysteriumnetwork/myst/). I can't figure out why but it appears to...

> @Lockie85 You can try to delete currently running container:  > > And then relaunch with newest docker image by running such command: `docker run --cap-add NET_ADMIN -d -p...

Humm, I can't seem to update. When I do so I'm forced to go through the onboarding process. My account doesn't seem to get picked up.

I'm using a Synology NAS on DSM 7 via Docker and so it works alittle differently. I can recover the container and view my account (Myst etc.) again.

Via the built in docker application: https://www.synology.com/en-uk/dsm/packages/Docker

I have this same issue on the follwing: Smartphone (please complete the following information): Device: Samsung Galaxy Tab A7 OS: Android 12 Applicaiton version [latest]