Skip to content
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

timeouts are keeping me from trading in China, possible to raise timeouts? #4220

Closed
jagottsicher opened this issue May 1, 2020 · 8 comments

Comments

@jagottsicher
Copy link

jagottsicher commented May 1, 2020

Description

ERROR occurs for at least 4 weeks now for every order I take:

An error occurred when taking the offer.

A timeout occurred.

No funds have left your wallet yet.
Please try to restart your application and check your network connection to see if you can resolve the issue.Please try to restart your application and check your network connection to see if you can resolve the issue.

Version

als version from 1.2.9 - 1.3.4

Steps to reproduce

Taking a sell order to buy btc

Expected behaviour

it shall work smootly like it did before

Actual behaviour

Error occurs (timeout)

Screenshots

Device or machine

Intel i3, Linux ubuntu 18.04 LTS with desktop Gnome

Additional info

In China you have to use VPN to tunnel through GFoC, nevertheless, I use TOR with the provides bitcoin Core nodes and Tor obfuscation V4. Problem occurs with both Astrill VPN and nordVPN and also without any VPN.

During startup for some weekd it talways takes quite long and after reaching connection 3/4 often the Tor-settings windows pops up. So it just takes quite long to connect.

Is it possible to extend the "time-to-live" to have a longer timeout tolerance?

bisq.log

@boring-cyborg
Copy link

boring-cyborg bot commented May 1, 2020

Thanks for opening your first issue here!

Be sure to follow the issue template. Your issue will be reviewed by a maintainer and labeled for further action.

@stale
Copy link

stale bot commented Jul 30, 2020

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.

@ripcurlx
Copy link
Contributor

This should be solved with #4233. Unfortunately because of the complexity of this PR testing & roll out will take some time.

@stale
Copy link

stale bot commented Oct 31, 2020

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 stale bot added the was:dropped label Oct 31, 2020
@ripcurlx
Copy link
Contributor

ripcurlx commented Nov 3, 2020

@jagottsicher Did the changes introduced in v1.4.2 improve your situation?

@stale stale bot removed the was:dropped label Nov 3, 2020
@ripcurlx
Copy link
Contributor

ripcurlx commented Dec 9, 2020

@jagottsicher ☝️

@stale
Copy link

stale bot commented Jun 11, 2021

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 stale bot added the was:dropped label Jun 11, 2021
@stale
Copy link

stale bot commented Jun 22, 2021

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.

@stale stale bot closed this as completed Jun 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants