Withdrawal to MetaMask - Error

[9vitorconti]

Dear Support, I have been trying to withdraw MYST to my Metamask Wallet from two nodes and it says "There was an error processing your your withdrawal please try again later" I did withdraw 3-4 weeks ago with no issues and in the past week I have been trying to withdraw literally every day but with no success. The issue happened at the same time on both nodes.

My nodes are in different networks and physical location and no changes were made to those nodes. It suddenly stopped working.

NODE1

• Node version: [1.2.2-7ebc1c52]
• OS: Ubuntu 20.04
• Node UI version [1.6.4]
• My Identity [0x91eff7164c49c379c12d5eb10ccbfd1030c9f8f8]
• Payment Channel: [0x9b7dA605A27995fBe5Ea499B0660Bd10e281c222]

NODE2

• Node version: [1.2.2-7ebc1c52]
• OS: Ubuntu 20.04
• Node UI version [1.6.4]
• My Identity [0x6e4243bec4f3060003706941a888d3e81e6a27b0 ]
• Payment Channel: [0x9b7dA605A27995fBe5Ea499B0660Bd10e281c222]

[tomasmik]

Hi, could you please provide node logs during the withdrawal process?

[etherunit]

@9vitorconti ping

[9vitorconti]

Dear Etherunit,

I am unable to send my node logs via GUI as it gives me the attached error message.

"could not create github issue: invalid character '<' looking for beginning of value (path="feedback/issue")"

I've been told that it was because my description was too short and this is why the error happened, however, I made a 300 character description and even doubled it up to 600 characters and I am still presented with the same issue.

Thanks,

On Wed, 6 Apr 2022 at 17:53, etherunit @.***> wrote:

@9vitorconti https://github.com/9vitorconti ping

— Reply to this email directly, view it on GitHub https://github.com/mysteriumnetwork/node/issues/4964#issuecomment-1089949079, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHIS5RWL3HGYXFQYFRGRTVTVDU7ITANCNFSM5SKMKDXQ . You are receiving this because you were mentioned.Message ID: @.***>

[etherunit]

Thanks for the explanation. Something is blocking it from the 3rd party. Please try to input your email, description and retry.

[9vitorconti]

Dear Etherunit,

Same error.

Any idea? Cheers

On Wed, 6 Apr 2022 at 18:18, etherunit @.***> wrote:

Thanks for the explanation. Something is blocking it from the 3rd party. Please try to input your email, description and retry.

— Reply to this email directly, view it on GitHub https://github.com/mysteriumnetwork/node/issues/4964#issuecomment-1089979417, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHIS5RTPNOCQZRGG6Z2BU6TVDVCDLANCNFSM5SKMKDXQ . You are receiving this because you were mentioned.Message ID: @.***>

[Guillembonet]

which browser are you using? @9vitorconti

[Guillembonet]

also try deleting the cookies in node ui and see if it helps, even if it does please let me know so we can fix it

[Lockie85]

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.

[Lockie85]

Could NAT issues cause problems like this one?

[Guillembonet]

@Lockie85 give us some more info, node version, node identity, did you enable auto withdrawals?

[Lockie85]

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 refuse to update to the latest version, I believe the version Im on is from January?

[Donatas-MN]

@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 4449:4449 --name myst -v myst-data:/var/lib/mysterium-node --restart unless-stopped mysteriumnetwork/myst:latest service --agreed-terms-and-conditions

Just make sure you keep Volumes part intact which holds backup data.

[Lockie85]

@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 4449:4449 --name myst -v myst-data:/var/lib/mysterium-node --restart unless-stopped mysteriumnetwork/myst:latest service --agreed-terms-and-conditions

Just make sure you keep Volumes part intact which holds backup data.

Thanks I'll give that a go. To be clear, what versions of "Node version" and "NodeUI version" should I be seeing?

[Donatas-MN]

These are the latest:

[Lockie85]

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.

[Donatas-MN]

In this case it means you've deleted "Volumes" part as well, so there is no backup anymore. But maybe you can just start a new node then?

[Lockie85]

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.

[Donatas-MN]

How did you start the node initially? I mean with what command? There is this part in the command stating where to store backup data: myst-data:/var/lib/mysterium-node. I guess you need to change to whatever you set in the beginning.

[Lockie85]

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

[Donatas-MN]

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

Ok, so you have to make sure that backup data folder is set to the same when you have started node. Can you also screenshot "Image" part of you docker console?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically closed because it has not had activity for a long time. If this issue is still valid, please ping a maintainer and ask them to label it as "pinned". Thank you for your contributions.