Must of have been a cache issue. It's working fine http and https.
I am running 220.127.116.11 now, but I don't think that changed anything regarding http/https cache.
Original post 2/6/19:
When I try to login to the hub via HTTP, it just presents the login page again.
When I try to login to the hub via HTTPS, it works. If I log out and try to login again using HTTP, it again just presents the login page again. It seems only HTTPS is working.
This is a screen recording using Loom showing this issue:
Unfortunately, Loom isn't showing when I change the URL from HTTP to HTTPS but HTTPS is the one in the video that is working and HTTP is the one that repeatedly shows the logon screen.
Edit: Google Chrome (71.0.3578.98) on Windows 10 (1803)
@halfrican.ak I initially saw this in Google Chrome (71.0.3578.98) on Windows 10 (1803).
I tried IE (11.523.17134.0) and it worked with HTTP and HTTPS without closing down the browser and killing it's processes. I tried closing and killing Chrome processes and when I launched it again, I saw the same issue.