Topic: Error 523 - Brazil (Read 2786 times)
It is working for me now.
...
Please anyone report, if you had error 523 trying to load https://en.bitcoin.it/
Is it fixed now - or is it still there?
Please anyone report, if you had error 523 trying to load https://en.bitcoin.it/
Is it fixed now - or is it still there?
Thanks for your help.
Yes, it works me now as well.
Its an important site for understanding, especially since it comes up constantly
in (my) Bitcoin question google searches. Thanks again.
Sorry, I just realized that they sent me a message on 13th of October, which I somehow missed.
It is possible though, that they fixed anyway.
Please anyone report, if you had error 523 trying to load https://en.bitcoin.it/
Is it fixed now - or is it still there?
Quote
This is not your account. Therefore I can not help. While we would like to assist you with your inquiry, for the security and privacy of our users we can only work with the account holder directly. If you are the website owner, and account holder, please submit a new support request from the email address you used to register your Cloudflare account. Note that you can also open a ticket directly through the Cloudflare dashboard following the below steps.
1. Log in to your Cloudflare account and click on 'Support' in the top right corner, which will take you to our Help Center.
2. Click on your name in the top right corner, and in the drop down menu select 'My Requests'.
3. Scroll to the bottom of the 'My Requests' page and click 'Submit new request' to submit your ticket.
We apologize for any inconvenience these extra steps may cause, but appreciate your patience and understanding to ensure the security and privacy of all our customers (including yourself).
Best Regards,
Kirk D. Washington II - Cloudflare Support Engineer
1. Log in to your Cloudflare account and click on 'Support' in the top right corner, which will take you to our Help Center.
2. Click on your name in the top right corner, and in the drop down menu select 'My Requests'.
3. Scroll to the bottom of the 'My Requests' page and click 'Submit new request' to submit your ticket.
We apologize for any inconvenience these extra steps may cause, but appreciate your patience and understanding to ensure the security and privacy of all our customers (including yourself).
Best Regards,
Kirk D. Washington II - Cloudflare Support Engineer
It is possible though, that they fixed anyway.
Please anyone report, if you had error 523 trying to load https://en.bitcoin.it/
Is it fixed now - or is it still there?
I submitted the traceroute's result to CF's support, but haven't heard from them ever since.
I assume they have looked into it by now.
I assume they have looked into it by now.
Hopefully it was a problem on their end and they fixed it in response to the traceroute.
Thanks for pursuing this issue!
Update: In Austria it now works again.
Thanks.I submitted the traceroute's result to CF's support, but haven't heard from them ever since.
I assume they have looked into it by now.
Update: In Austria it now works again.
I have the same issue in Austria for several weeks now.
Tried from my notebook and mobile phone from 3 different networks (2 static, 1 mobile), always with the same cloudflare error 523 page as posted in #4 (except that in my case the Cloudflare node(?) isn't labeled POP:undefined, but Vienna).
$ traceroute en.bitcoin.it
traceroute to en.bitcoin.it (104.25.118.16), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 0.886 ms 1.133 ms 1.910 ms
2 * * *
3 84.116.5.33 (84.116.5.33) 18.297 ms 18.915 ms 18.995 ms
4 at-vie01a-rd1-ae26-2031.aorta.net (84.116.228.81) 27.291 ms 28.924 ms *
5 * * *
6 * 213.46.184.6 (213.46.184.6) 18.874 ms 23.685 ms
7 cloudflare-ic-316117-win-b4.c.telia.net (62.115.144.85) 24.936 ms 24.967 ms 25.083 ms
8 104.25.118.16 (104.25.118.16) 24.689 ms 24.512 ms 24.649 ms
Btw. http://downforeveryoneorjustme.com/en.bitcoin.it tells me: It's not just you! http://en.bitcoin.it looks down from here.
Tried from my notebook and mobile phone from 3 different networks (2 static, 1 mobile), always with the same cloudflare error 523 page as posted in #4 (except that in my case the Cloudflare node(?) isn't labeled POP:undefined, but Vienna).
$ traceroute en.bitcoin.it
traceroute to en.bitcoin.it (104.25.118.16), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 0.886 ms 1.133 ms 1.910 ms
2 * * *
3 84.116.5.33 (84.116.5.33) 18.297 ms 18.915 ms 18.995 ms
4 at-vie01a-rd1-ae26-2031.aorta.net (84.116.228.81) 27.291 ms 28.924 ms *
5 * * *
6 * 213.46.184.6 (213.46.184.6) 18.874 ms 23.685 ms
7 cloudflare-ic-316117-win-b4.c.telia.net (62.115.144.85) 24.936 ms 24.967 ms 25.083 ms
8 104.25.118.16 (104.25.118.16) 24.689 ms 24.512 ms 24.649 ms
Btw. http://downforeveryoneorjustme.com/en.bitcoin.it tells me: It's not just you! http://en.bitcoin.it looks down from here.
Guys, I have moved recently and I don't experience this problem anymore from where I am now.
Whoever is facing the issue, could you please capture a traceroute from your location to a cloudflare server and post it here?
Like they say:
I have a support ticket open at CF - if I get the info, I can push it forward.
Whoever is facing the issue, could you please capture a traceroute from your location to a cloudflare server and post it here?
Like they say:
Quote
a useful piece of information to give to CloudFlare's support team is a traceroute between your origin and one of CloudFlare's IP addresses (ideally one of the addresses that you usually see send requests to your site).
I have a support ticket open at CF - if I get the info, I can push it forward.
I'm getting the same error and had this problem for a few weeks now.
I though the site was down for good until I found this thread.
Someone who knows the admins emails should contact
and let them know half the world can not view the site.
I though the site was down for good until I found this thread.
Someone who knows the admins emails should contact
and let them know half the world can not view the site.
They answered:
Quote
Thank you for contacting Cloudflare Support. I am sorry to hear that you are experiencing some difficulties here.
If you are seeing an Error 523, it means that there is an issue from the origin web server, as it's unreachable.
A common cause is that the DNS setting has changed. Sometimes, hosting providers update the origin IP information for their customers. If this is the case, you need to make sure the new origin IP address for your A record is reflected in your CloudFlare DNS Settings page. Once make the change in your CloudFlare DNS Settings page, wait up to 5 minutes for it to take effect.
Another common cause of 523 errors are internet routing issues between CloudFlare's systems and the origin (i.e. the web server where the site is hosted). This can be caused by issues with an internet provider between your origin and CloudFlare, or with the origin itself. If you are confident this isn't caused by your web hosts, a useful piece of information to give to CloudFlare's support team is a traceroute between your origin and one of CloudFlare's IP addresses (ideally one of the addresses that you usually see send requests to your site). You can find instructions on running a traceroute test here. That should help them to pinpoint the issue.
523 errors can also be caused by Railgun. If you are the customer of a Hosting Partner of CloudFlare and you are using their Railgun, you should contact them about this. If you are running your own Railgun, then you should contact CloudFlare's support team, providing the most recent syslog file from your Railgun server if that's possible.
If you are seeing an Error 523, it means that there is an issue from the origin web server, as it's unreachable.
A common cause is that the DNS setting has changed. Sometimes, hosting providers update the origin IP information for their customers. If this is the case, you need to make sure the new origin IP address for your A record is reflected in your CloudFlare DNS Settings page. Once make the change in your CloudFlare DNS Settings page, wait up to 5 minutes for it to take effect.
Another common cause of 523 errors are internet routing issues between CloudFlare's systems and the origin (i.e. the web server where the site is hosted). This can be caused by issues with an internet provider between your origin and CloudFlare, or with the origin itself. If you are confident this isn't caused by your web hosts, a useful piece of information to give to CloudFlare's support team is a traceroute between your origin and one of CloudFlare's IP addresses (ideally one of the addresses that you usually see send requests to your site). You can find instructions on running a traceroute test here. That should help them to pinpoint the issue.
523 errors can also be caused by Railgun. If you are the customer of a Hosting Partner of CloudFlare and you are using their Railgun, you should contact them about this. If you are running your own Railgun, then you should contact CloudFlare's support team, providing the most recent syslog file from your Railgun server if that's possible.
So, they're basically telling you that a wiki admin needs to take care of this, because all solutions have to be done by somebody with either access to the server or access to the cloudflare account of the wiki...
They answered:
Quote
Thank you for contacting Cloudflare Support. I am sorry to hear that you are experiencing some difficulties here.
If you are seeing an Error 523, it means that there is an issue from the origin web server, as it's unreachable.
A common cause is that the DNS setting has changed. Sometimes, hosting providers update the origin IP information for their customers. If this is the case, you need to make sure the new origin IP address for your A record is reflected in your CloudFlare DNS Settings page. Once make the change in your CloudFlare DNS Settings page, wait up to 5 minutes for it to take effect.
Another common cause of 523 errors are internet routing issues between CloudFlare's systems and the origin (i.e. the web server where the site is hosted). This can be caused by issues with an internet provider between your origin and CloudFlare, or with the origin itself. If you are confident this isn't caused by your web hosts, a useful piece of information to give to CloudFlare's support team is a traceroute between your origin and one of CloudFlare's IP addresses (ideally one of the addresses that you usually see send requests to your site). You can find instructions on running a traceroute test here. That should help them to pinpoint the issue.
523 errors can also be caused by Railgun. If you are the customer of a Hosting Partner of CloudFlare and you are using their Railgun, you should contact them about this. If you are running your own Railgun, then you should contact CloudFlare's support team, providing the most recent syslog file from your Railgun server if that's possible.
If you are seeing an Error 523, it means that there is an issue from the origin web server, as it's unreachable.
A common cause is that the DNS setting has changed. Sometimes, hosting providers update the origin IP information for their customers. If this is the case, you need to make sure the new origin IP address for your A record is reflected in your CloudFlare DNS Settings page. Once make the change in your CloudFlare DNS Settings page, wait up to 5 minutes for it to take effect.
Another common cause of 523 errors are internet routing issues between CloudFlare's systems and the origin (i.e. the web server where the site is hosted). This can be caused by issues with an internet provider between your origin and CloudFlare, or with the origin itself. If you are confident this isn't caused by your web hosts, a useful piece of information to give to CloudFlare's support team is a traceroute between your origin and one of CloudFlare's IP addresses (ideally one of the addresses that you usually see send requests to your site). You can find instructions on running a traceroute test here. That should help them to pinpoint the issue.
523 errors can also be caused by Railgun. If you are the customer of a Hosting Partner of CloudFlare and you are using their Railgun, you should contact them about this. If you are running your own Railgun, then you should contact CloudFlare's support team, providing the most recent syslog file from your Railgun server if that's possible.
Maybe you can try to contact cloudflare's support and see if they can help you out?
ok, done - now waiting...
I see it's a cloudflare error message... This article might be usefull:
https://support.cloudflare.com/hc/en-us/articles/200171946-Error-523-Origin-is-unreachable
Especially this piece:
Maybe you can try to contact cloudflare's support and see if they can help you out? The traceroute has to be started from the origin tough, so you'll need an admin of the wiki to help you out to i'm afraid...
https://support.cloudflare.com/hc/en-us/articles/200171946-Error-523-Origin-is-unreachable
Especially this piece:
Quote
If you are confident this isn't caused by your web hosts, a useful piece of information to give to CloudFlare's support team is a traceroute between your origin and one of CloudFlare's IP addresses (ideally one of the addresses that you usually see send requests to your site). You can find instructions on running a traceroute test here. That should help them to pinpoint the issue.
Maybe you can try to contact cloudflare's support and see if they can help you out? The traceroute has to be started from the origin tough, so you'll need an admin of the wiki to help you out to i'm afraid...
It's same here, in Greece.
Does anyone has the wiki working ATM?
Does anyone has the wiki working ATM?
Works without a glitch from western-europe...
OK, thanks.
So I guess nobody's going to fix it for us
It's same here, in Greece.
Does anyone has the wiki working ATM?
Does anyone has the wiki working ATM?
Works without a glitch from western-europe...
It's same here, in Greece.
Does anyone has the wiki working ATM?
Does anyone has the wiki working ATM?
bitcoin.it is unreachable in Brazil. I get Error 523: Origin is unreachable. This problem has been occurring for a long time.
People are discussing about this problem here (in Portuguese): https://bitcointalksearch.org/topic/wiki-bitcoinit-fora-do-ar-1522056.
Does anyone know why this is happening?
People are discussing about this problem here (in Portuguese): https://bitcointalksearch.org/topic/wiki-bitcoinit-fora-do-ar-1522056.
Does anyone know why this is happening?
Jump to: