You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when you click on the "Buy Skycoin directly with BTC" on the https://www.skycoin.net/markets/ page, you get the following error:
This site can’t be reached
otc.skycoin.net refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
This could be very damaging - it makes us look like we do not know what we are doing for anyone who checks.
As a quick fix, we should have a friendly down page for OTC which says something like:
We are currently developing the next generation teller application for skycoin.
In the mean time, please use one of these services to purchase skycoin
=> c2cx
etc.
To put this live, we could either:
change the link on the markets page (wont work for bookmarks and search pages)
setup a redirect of any page to the new down page using the hosting control panel (e.g. cloudflare, Amazon S3 etc) or a htaccess or similar if the site is hosted on a real webserver.
replace the current index page on the otc server.
A second later phase of this would be for the skycoin.net page to check the status of the otc server and not put the link there if it is down (instead give a friendly message).
The text was updated successfully, but these errors were encountered:
Currently, when you click on the "Buy Skycoin directly with BTC" on the https://www.skycoin.net/markets/ page, you get the following error:
This could be very damaging - it makes us look like we do not know what we are doing for anyone who checks.
As a quick fix, we should have a friendly down page for OTC which says something like:
To put this live, we could either:
A second later phase of this would be for the skycoin.net page to check the status of the otc server and not put the link there if it is down (instead give a friendly message).
The text was updated successfully, but these errors were encountered: