How to fix the JIRA customer portal when its showing a blank page?

[Deleted user]

One user in our company is the only one having this issue. The service desk is showing a blank screen on the portal. One user had this and a laptop shut down and turn back on solved the problem, but I tried the same for Mary but the issue persists. I tried multiple browsers but the problem remains. Updated her Chrome but still, the customer portal is showing a blank page.

[Karen Briody]

We also have a similar issue with customers who are logging into their portal that it comes up with blank screen, but not every time.  It appears to be a sporadic issue for her.   

Has anyone found a solution?

[Phil Evans]

no official solution i guess

but!
i think i came up with some kind of solution.

lets say your jira sd instance is jira.com
when portal users go to jira.com - blank screen
if they go to jira.com/secure - then the token is updated - they can login here or go back to portal login and it will show up. so, yes theres a solution to go to /secure

but what im thinking about is - redirect all requests to jira.com to jira.com/secure. then portal users will be able to login and will be redirected to portal, if logged in already - redirected automatically to portal. if sd agent - thats where agent wants to go anyway.

will discuss with sysadmins and test today

[Phil Evans]

well, yes, it does make sense if user goes straight to jira.com to access portal and is redirected to jira.com/secure to avoid blank screen.

but if user has a link to his raised request on portal and he was not logged in for a long time, then redirection to /secure doesnt really make sense. he will be able to avoid blank screen, but the link to his raised request will be lost i guess. maybe this can work if to come up with right logic for redirection.

[Phil Evans]

not a good solution

[Phil Evans]

Samuel, have you found out why portal behaves like this?

We have similar problem.

[Brant Schroeder]

If you look in the chrome dev console, is there any errors? You could also try enabling the network tab and checking to see if there are any requests that are returning errors.

Does the user have javascript disabled?