<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=19126) </details> <!--IssueSummary end--> As a follow up to https://gitlab.com/gitlab-org/gitlab-ce/issues/33220#note_32262075, now that https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/11449 has been merged, I'd like to ask our UX team to take a look at what the experience is of an NFS drive going down: if I understand correctly it will throw a 502 error to the individuals impacted. This includes anyone for whom the URL they are accessing seeks access to the downed NFS drive. How hard would it be to do a little better than a 502, for instance populating those parts of the URL that _can_ be populated and providing a more detailed insight into what is missing / why? \cc @sarrahvesselov @reprazent