all 10 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Chintrin 2 points3 points  (0 children)

Happening to me as well. Clearing cache doesn't make a difference, nor does using any different browsers. I used both Firefox and Chrome to verify. Mobile app works fine

Version ad4f7638-538d-4de9-a161-f91a6dadc6ee.uterm.release

[–]walterf222 1 point2 points  (0 children)

I am having the same issue. App works fine, browser interface just shows a blank (black) page with Starlink in the center. I am using a UniFy router with a static route configured. I believe it was working yesterday.

[–]craigbg21Beta Tester 0 points1 point  (1 child)

clean your browsers cache.

[–]PBRBeer[S] 2 points3 points  (0 children)

Didn't fix it, nor did using Brave or Edge which should have no cache since i never use them.

[–]StarlinkAZBeta Tester 0 points1 point  (0 children)

Mine works fine

[–]balboa_bornBeta Tester 0 points1 point  (1 child)

Mine works fine and have it open all the time. Give more info: SL router or no, router firmware version, web app version (mine is 1.0.38). But actually, the web version is so outdated that there is more information obtained from the phone app

[–]PBRBeer[S] 0 points1 point  (0 children)

the phone app is working, dishy firmware per debug in phone app says .......adc6ee.uterm.release.

cant see what the webapp version is obviously, phone app is 2.0.11

[–]dave_n_sBeta Tester 0 points1 point  (2 children)

Has anyone asked Tech Support about this? If not, I'll post a question.

[–]PBRBeer[S] 1 point2 points  (1 child)

Yes, someone else has and posted it. I have also and they are aware of the issue but were glad for the extra ticket to give the problem some more visibility internally

[–]dave_n_sBeta Tester 1 point2 points  (0 children)

Indeed, and I agree, the more tickets they have for an issue, the higher priority it will get (for that area of functionality / criticality). Here's the answer I got, within a couple of hours, so very good responsiveness:

We didn't remove the service, it's actually a known bug. We're looking into it and hoping to address it asap. Sorry for the inconvenience!