Finding Ream Network Errors on Your Computer

My Computer is Possessed! 😱


In order to assist you in receiving the best possible technical support from Ream, sometimes we will need to see the network errors on your browser when a specific Ream page loads.



Here's how you can find the network errors in Safari:


1: To enable the Developer Menu in Safari, go to Safari Menu > Preferences.


2: In the Advanced Tab, click Show Develop menu in the menu bar.


3: Once this function is enabled, go to the desired webpage and find the developer console by clicking on Develop > Show Javascript Console, or use the shortcut Option + ⌘ + C.


4: To open the Network logs, switch to the Network tab and refresh the webpage. Errors are displayed in red.


5: Click on the error to open the details. You can find critical error information in Preview and Headers tab. Please check with your designated support agent to determine which information to share.


Then if you can screenshot this — that would be amazing! 🙏 We will look for the red errors that are displayed so that we can fix this issue for you 🙂.



For Chrome, you can do the following:


1: First right-click. If on MacBook "right click" or click with both fingers. 


2. Hit Inspect from the options that pop up to click.


3: Then go to the network tab and screenshot the errors.


OR you can go to:


1: The three dots in the top right corner of your browser.


2: At the bottom click More tools >> Developer Tools


3: Then go to the network tab and screenshot any red errors.



For Edge:


The process is much the same as for Chrome. Here's the path:

Three dots upper right side> More tools> Developer tools> Network tab (little WiFi icon)


Then look for an errors on the lower left side (you may need to scroll), click on each one, and screenshot what each one says.


If you need further assistance or have questions, contact our Support team at support@reamstories.com

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us