OutagesIO Support Forums
Information, Support, and FAQ relating to OutagesIO. Monitor your Internet service and provider with optional alerts to connection issues or downtime. For home, small businesses, IT companies, and enterprises. Tracks Internet and provider reliability with useful proof. For Windows, Linux, ARM (Raspberry, Tinker Board, etc).Learn more by visiting www.outagesio.com
SOLVED: Cannot access dashboard | 503 and 504 errors
-
@OutagesIO_Support
I have not been able to reach my dashboard on "https://app.outagesio.com/agent/dashboardUnified/id/128855" for more than a week now.
Don't know what to do.
It used to work for months/years.In my chrome browser I get a timeout.
In a incognito-window (chrome) I get the login-form, but after logging in with my credentials I get the time-out.On my mobile using the internet of my mobile-provider, I have the same.
Cannot reach any webpage from app.outagesio.com.
So I do not think it is my LAN.I have created an alert on "https://uptimerobot.com/" to see if the dashboard-webpage is up, and they can reach the webpage.
What can ?I do next?
-
@OutagesIO_Support said in Cannot access dashboard | 503 and 504 errors:
Unfortunately, you have not shared any new information and I had asked a few things to try and help.
I'm not really sure how to diagnose this. I've tried it from different browsers, different networks, different PC's and all work as they should.
A dev that works remotely from Argentina has been working on this upgrade all week. A dev that is in the UK has also been working on something.
As you might notice in another post, we've even developed a new installation method during the last few days and there are posts from other members in the forums talking about installation help and they can reach the service.
The service was never completely down, it was interrupted during the week+ long upgrades/changes that we had to make.
Are you saying you still cannot access it now? If so, have you tried something like TOR? Maybe it's something between your location and the data center in Phoenix.
We're more than happy to help but we need more information in order to do so because everything is up and running.
I tried to signup with a new account.
I received the confirmation email, but then again I can not activate it
When clicking "https://app.outagesio.com/account/activate/user_id/6633/token/ab49b5e0258fc475b4f53ab5f53ead6d" I get a timeout..... -
@OutagesIO_Support said in Cannot access dashboard | 503 and 504 errors:
Unfortunately, you have not shared any new information and I had asked a few things to try and help.
I'm not really sure how to diagnose this. I've tried it from different browsers, different networks, different PC's and all work as they should.
A dev that works remotely from Argentina has been working on this upgrade all week. A dev that is in the UK has also been working on something.
As you might notice in another post, we've even developed a new installation method during the last few days and there are posts from other members in the forums talking about installation help and they can reach the service.
The service was never completely down, it was interrupted during the week+ long upgrades/changes that we had to make.
Are you saying you still cannot access it now? If so, have you tried something like TOR? Maybe it's something between your location and the data center in Phoenix.
We're more than happy to help but we need more information in order to do so because everything is up and running.
Newly created user seems to work in chrome incognito mode:
-
@OutagesIO_Support
Removed all outagesio related cookies in my chrome browser and everything seems to work now for both new and existing user....... -
Please let me know if you are still experiencing the same issues now
-
@SBK
dashboard at app.outagesio.com is ok now!www.outagesio.com gives a timeout now.
-
@SBK
Can not see dashboard at https://app.outagesio.com/agent/dashboardUnified/id/128915 now
Gateway Timeout..... -
So it is definitely something related to DNS replications at this point
Let us check a bit more why this is affecting some regions only -
Actually, no DNS changes had to be made for this move other than the dnspoints slave server which is only used for members DDNS.
On this end of the network, other than a database issue that lasted around an hour yesterday, the only issues we still have is a slowness between servers due to heavy traffic that is being worked on.
Nothing else should affect the service other than in short burps so this problem is very perplexing.
-
There seemed to be a problem with cookies and local browser data. I am accessing the dashboard using a windows PC and a macOS PC, on both Chrome and Firefox. Accessing it via Incognito/Private Browsing allows me to log back in. Little bit of inconvenience but for almost 2 weeks I thought the dashboard was down. Probably something with the DNS issue you guys have raised.
P.S.
Yes it is still ongoing for me. I haven't cleared my local cache and I am willing to send it to you guys for debugging.Update:
Tried to login to Incognito on Windows PC and got hit with another 504 error.Update #2:
Tried connecting via VPN located at Singapore and London. Still can't login. Gateway timeout still. -
Here's some more info and screenshots:
I can access the login page using Private Browsing/Incognito. But once I submit my login credentials I encounter 504 Gateway Error.
-
Unable to login to the dashboard for at least 5 hours this morning using various browsers. I got in once on Sunday, but mostly got the same error.
Gateway Timeout
The gateway did not receive a timely response from the upstream server or application.
-
Hi,
That's so strange. Not doubting you at all, just not sure how to diagnose this. We have a similar problem with another person trying to get their agent to work but it cannot reach the receiving servers.
We know there is a gateway issue which is something we've been working on for days but it's not consistent, it's random, and it doesn't take the entire site down, just now and then.
We've been monitoring everything internally non stop and do see some latency problems and know when there are complete disconnections between app/db servers and so on but we reset those as quickly as we learn about them.
There must be something members are seeing that we simply haven't caught which is odd considering we're using the service from remote too so would experience the same things.
Still digging and definitely appreciate your ongoing input on this.
-
Still get the same error when attempting to login to my own account, BUT strangely I CAN login to the demo account! So is it some problem specific to my account?
I tried to do a password reset both using my email address and my username and in both cases it said it had sent a reset to my correct email address (so it knew the correspondence between the two) but nothing has arrived after 10 minutes, and yes I have checked my spam.
-
Hi,
We can see in the email logs that the emails are making it into the site, which appears to be Google.
The email is not bouncing back so maybe the email service is quietly blocking outagesio.com?Have you tried sending a reply to us and whitelisting it from the same mail service? Just send an email to noreply@outagesio.com. Even if it bounces, it'll whitelist the service.
/var/log/smtp.log:Apr 5 10:53:12 mx postfix/smtp[29689]: DAFD9AE798: to=<xxxxx@xxxxx.org.uk>, relay=aspmx.l.google.com[172.217.194.27]:25, delay=3.1, delays=0.01/0/1.8/1.3, dsn=2.0.0, status=sent (250 2.0.0 OK 1649181191 f13-202a792ed00159ba2i4079lg.326 - gsmtp) -
Hi Mike,
Since I have no way to access to your dashboard may I ask you your permission to force-change your password so i can test it? -
Well that's interesting. I've managed to get the password reset email and reset it to the same password. It then automatically logged me in and I could see my dashboard.
So I logged out and tried to login again and I am back to getting the error!
-
Sorry, messages crossed. Yes go ahead and force change the password.
-
@mikeshand
I will send it to your email address so we can both test and double check -
The new password gives the same gateway timeout error for me.
