Can only see a pitch black screen

I have used both Chrome and Firefox and get the same result from both, a pitch black screen sometimes seeing my token.  We have tried everything to get it to show the game board but nothing works. My character is the only one that is having this issue in our group and I am all out of ideas.

Without knowing exactly what you have tried, I can only offer a general checklist: Verify that the token on the board represents your character. An incorrectly set up or placed default token may not retain its reference. Does the token have sight? Is there a light source on the board, unobscured by a DL wall. If not, does the token emit its own light? Is the GM using (regular) Fog of War (can't remember the exact name of this feature in UDL)? If so, is your token in an are that has not been cleared? Is your token on the Objects layer? Are you using a supported browser: Chrome or Firefox? Have you tried turning off extensions (A private browsing window can likely do this for you)?

Does "a pitch black screen" literally mean that? You can't see the sidebar, your browser menu, taskbar... nothing? Or you mean just the tabletop is black? If it's just the canvas, ask the GM to give you permission on another player's character that is working. Can you see now? Then the token is the problem. Also let your GM know, if they don't already, that they can shift + long-left-click to centre all players' views to the spot on the map. That way they can make sure you're not just staring at the wrong side of the map, which is supposed to be unexplored. If your entire screen is black it is almost certainly your PC that needs attention.

A more rare situation to check is to ask your GM to be sure you are not split from the other players on another page. See Split the Party here: <a href="https://roll20.zendesk.com/hc/en-us/articles/360039675413-Page-Toolbar#PageToolbar-SplittheParty" rel="nofollow">https://roll20.zendesk.com/hc/en-us/articles/360039675413-Page-Toolbar#PageToolbar-SplittheParty</a> More than likely it's a token settings issue and Keith's and Oosh's suggestions will get you sorted.