Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Cannot Connect to Roll20

I have been having this issue since yesterday around 1800 CST. Attempting to access any of my existing campaigns that I act as host or player results in an endless loading screen. I left it up over night with no success. Attempting to create a new game ends in the same result. I am using chrome and have cleared my cache and cookies with no change. I created a new campaign with no effect. Changing browsers to Firefox had no effect. Utilizing my VPN to connect through different countries had no effect.  I am open to other options.
1609949529
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
You can probably narrow down some possibilities by creating a  Dummy Account  and seeing if you can load/create a campaign with that. It would at least show that it is not a hardware or connection problem and something specific to your account. The VPN seems to rule out the issue that users of the Telekom ISP have had. Assuming you were using a fresh install of Firefox, this would rule out extension conflicts, but trying a Private Browsing window would help verify that. Capturing a Console Log and filing a  Help Center Request  would be a good avenue to take. I am posting the Troubleshooting instruction below (most of these you have done) since Step 4 tells how to capture a Console Log. Could you please carefully work through these steps of our guide to  Solving Technical Issues ? Step 1: Make sure to use the right browser Please check if these issues persist when using both Chrome  and  Firefox. Step 2: Ensure that there are no extensions/addons interfering with Roll20 Please disable  all  add-ons/extensions. Step 3: Clear your cache If none of the above succeeds, please thoroughly work through  Step 4 .  (Don't forget the complete Console Log!)