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 here.
×
×
Cookie Preferences
We use Cookies to help personalize and improve Roll20. For more information on our use of non-essential Cookies, visit our Privacy Policy here.
By the way, comparing the console log of a failing computer to a working computer, this seems to be the issue: app.roll20.net/:14 GET <a href="https://browser.sentry-cdn.com/5.15.4/bundle.min.js" rel="nofollow">https://browser.sentry-cdn.com/5.15.4/bundle.min.js</a> net::ERR_CONNECTION_REFUSED
Some more notes: Using Wireshark, connections to the sentry-cdn.com are continually reset. Safari on iOS does work, even over the same internet connection. For the record, I'm using no extensions on Chrome, and have also tested on Edge, Safari (on a mac), and Chrome (on a mac)
Ok, after comparing Wireshark logs on the computer that was working and the computer that was not, I spotted some inconsistencies in the requests and the TCP/IP addresses. So I tried this fix: Successful Fix for Windows: Open a command prompt Issue the command: ipconfig /flushdns Reload the page... This may resolve the issue, assuming the DNS servers you are using are updated to the new set of IP addresses. If not, try the Google DNS (8.8.8.8,8.8.4.4) as I know they are up to date.
What flushdns does is clear your cached local copy of resolved DNS addresses, forcing your computer to look them up again. The reason it slowed your browser is it had to look up every new address for a little while (Many webpages load sources from multiple other pages, so it has a big impact for the first 30 minutes or so) I'm not sure what you mean about a DOS command for setting the DNS. nslookup will look up a DNS address via the DOS prompt. If you give it an authoritative host, it will look it up using that host instead of using the local cache.