Want more timely Centmin Mod News Updates?
Become a Member

Forum connectivity issues 502 timeouts etc ?

Discussion in 'Forum Feedback & Suggestions' started by eva2000, May 1, 2017.

Tags:
  1. eva2000

    eva2000 Administrator Staff Member

    28,987
    6,579
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +9,767
    Local Time:
    12:04 PM
    Nginx 1.13.x
    MariaDB 5.5
    Past few days seems this forum is having connectivity issues or slowness with 502 timeouts from certain geographical locations to this forum's Sucuri Cloudproxy frontend.I've contacted Sucuri support already to see if it's a problem at their end. For me it's from Sydney = 502 timeout. But Brisbane fine for me but guess it could be other routes to Sucuri.

    If you are having similar issues, please private message me a mtr report from your location to my forums if you can.

    If on linux install mtr
    Code (Text):
    yum -y install mtr
    

    using command
    Code (Text):
    mtr --report community.centminmod.com
    


    If on windows use winmtr WinMTR – Free Network Diagnostic Tool

    Please mention your location too.
     
    • Informative Informative x 1
  2. joshuah

    joshuah Member

    115
    14
    18
    Apr 3, 2017
    Ratings:
    +16
    Local Time:
    12:04 PM
    I am in Sydney and have not noticed any issues and i am on here quite often.
     
  3. eva2000

    eva2000 Administrator Staff Member

    28,987
    6,579
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +9,767
    Local Time:
    12:04 PM
    Nginx 1.13.x
    MariaDB 5.5
    Yeah it's only some routes geographically and seems to be from some of Sucuri's locations i.e. Tokyo, Sydney and @RoldanLT reports from Philippines

    seems to be better for me right now from Sydney and Brisbane locations
     
    • Like Like x 1
  4. eva2000

    eva2000 Administrator Staff Member

    28,987
    6,579
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +9,767
    Local Time:
    12:04 PM
    Nginx 1.13.x
    MariaDB 5.5
    seems the issue has cleared up for me in Sydney region access :)