Closed damithc closed 2 months ago
I sometimes encounter this problem as well, when I paste the Heroku URL directly into the browser, it cannot redirect to the Heroku page, with ERR_CONNECTION_RESET
error. I think this has something to do with the gatekeeper rather than CATcher. I'm not too sure when exactly it happens.
Is it possible NUS is blocking our Heroku app? Perhaps you can try using your non-NUS connection to check if the problem is specific to NUS network?
Folks, can you try to reproduce the problem from within
Hi, Prof. I'm currently outside of NUS and tried logging in and out CATcher over 10 times, even triggering GitHub reauthorization, but still couldn't reproduce the problem.
@NereusWB922 Thanks. I think it is fairly certain the problem doesn't happen outside of NUS. The main worry is NUS network, within SoC. Myself and another person was able to reproduced it earlier but not sure how it is now (I'm not in SoC now).
I'm currently in NUS but not in SoC, but unable to reproduce the problem. I previously encountered this problem both in SoC and outside SoC, but usually I can log in after ~10 mins.
CATcher works when I'm in UTown.
Not entirely sure if this is related but I tried logging into the SoC VPN via Forticlient on my Mac using Sonoma 14.1.1 but I couldn't login either. Maybe it's an SoC internet issue?
Even after waiting for about 30 minutes, I still get the "Network error. Can not connect to VPN server." Wonder if it is an SoC side issue? Is there a way to raise this with the IT team?
Update: I am able to connect through the Forticlient VPN to SoC's network. I am able to login to CATcher tutor's group.
Unfortunately, I won't be in COM today to physically test it, but hopefully that is a +1 data point for debugging
Currently connected to NUSSTU at COM3, gatekeeper seems to work as of 10.04 am
Our server logs on heroku did not indicate anything unusual at 4/17/2024, 6:42PM GMT+8, but there was no record of any API request at that time
Thanks for your inputs so far.
Based on what we've seen so far, the problem seems to have happened around Thu 6-8.30pm. It wasn't just me because I got the tutor of another course to confirm. In fact, it was he who noticed that the problem doesn't happen if he uses the mobile hotspot. After that, both of us went out of SoC and tested from other locations in NUS, and the problem didn't happen there. This made us think the problem was local to SoC but it is also possible that the problem got resolved just at that time, giving us a wrong impression.
This problem period coincided with STePS. Perhaps some activities going on there caused a blockage/throttling to kick in on NUS network or on Heroku side?
Our server logs on heroku did not indicate anything unusual at 4/17/2024, 6:42PM GMT+8, but there was no record of any API request at that time
I guess this means the requests were blocked before reaching Heroku?
Eduroam, NUS_STU in biz, same issue
NUS_Guest seems to work
Same issue on NUS_STU (Yale-NUSC Library), switching to my mobile phone's hotspot seemed to remedy the issue.
Oh im getting error connection reset at COM3 now (6pm)
Follow tests were done in this order at COM3 between 6.01pm - 6.06pm:
I can't connect to the SoC VPN either. This may be a network issue in SoC
Yup, I'm facing it right now, in COM2. It was working fine for the whole day though.
Got this error using NUS_STU @ UTown (before the prompt to continue with GitHub account) which went away when I used my mobile hotspot.
Same error within the last 10 minutes.
NUS Utown (Residential colleges (RC1/Saga College) dorm wifi)
Works on Singtel Mobile data
I've notified SoC IT. They are able to reproduce the problem, and and looking into it.
NUS_STU at Utown. Error occurs.
Connected to NUSSTU at Engineering. I get the same error message.
Update: NUS IT says they whitelisted our Heroku app. Check again when you have a chance (from inside an NUS network) and let us know if it is working now.
No issues during the PE. Closing...
I'm getting this kind of error when I try to login to CATcher. Sometimes I get through, but most times it errors out. Seems like a problem with authentication (via heroku).
Example log:
@chunweii @vigneshsankariyer1234567890 @luminousleek @gycgabriel @cheehongw @NereusWB922 @Arif-Khalid @nknguyenhc @MadLamprey
We need to solve this urgently, as the PE is this Friday. Frist of all, let me know if you can reproduce the problem.