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
Describe the bug
I noticed the Gateway sends a different HTML page when the internet connection is erroneous.
To Reproduce
Have a bad internet connection - I don't know yet what specifically needs to be set for this to happen.
Load localhost:5000
Expected behaviour
The login page to appear
Actual behaviour
A different page appears:
Environment
IBeam version: 0.3.0
Python version: 3.7
OS: Windows 10
Additional context
This started appearing today on the same network I used to load localhost:5000 login page without any issues. We noticed the internet being slow today - so this could somehow be linked to this replacement page being displayed.
If anyone else understands why this appears - leave some comments below and help us understand this issue.
The text was updated successfully, but these errors were encountered:
hey @RichiePBot interesting to know! I thought I was alone. But no, I still have no idea why this happens. Opened this issue to have some way of tracking information on this issue.
I'm going to close this issue due to inactivity. Thanks for your contribution and please feel free to request a reopen if you'd like to continue the discussion 👍
Describe the bug
I noticed the Gateway sends a different HTML page when the internet connection is erroneous.
To Reproduce
Expected behaviour
The login page to appear
Actual behaviour
A different page appears:
Environment
IBeam version: 0.3.0
Python version: 3.7
OS: Windows 10
Additional context
This started appearing today on the same network I used to load localhost:5000 login page without any issues. We noticed the internet being slow today - so this could somehow be linked to this replacement page being displayed.
If anyone else understands why this appears - leave some comments below and help us understand this issue.
The text was updated successfully, but these errors were encountered: