0

Oops, we have encountered a temporary glitch error upon logging in SUPPORT-679

Description:

2014-04-10_1722.png

Users are receiving an "Oops, we have encountered a temporary glitch" error after logging in at the URL members.webs.com/sites/?from_login=1

If you are seeing an error that starts with "Sorry", please click here to go to the support topic on your separate issue.

Important Information:

In an effort to get this challenging issue resolved as quickly as possible there is some additional information you can provide if the error does not go away after a few minutes. Please see the following troubleshooting tips.

Troubleshooting Steps:

The following steps assume you have already tried closing your browser, clearing your cache, and starting a new session. As you know, clearing your browser's cache is always the first step in troubleshooting.

  1. Download Google Chrome so you can use the Chrome Console feature. Chrome can be installed for free by clicking here: chrome.com
  2. Open Google Chrome once it's installed and hit the F12 key on your keyboard. This will launch the console in the bottom half of your browser window.
  3. By default the console will open to the "Elements" tab. Please click on the Console tab.
  4. Attempt to access your Webs account just like you normally would.
  5. Once you see the error message take a screenshot of the full browser window, including the console and your address bar.
  6. Lastly, go to http://www.webs.com/testServer.jsp and take a screenshot of the results.
  7. If you are willing to chat with our support team to further troubleshoot this between 11AM-4PM EST Monday to Friday, please provide your contact email address.

Once you have gathered all of this information please share the screenshots as well as your Webs site address in this thread. This will also subscribe you to this topic so you'll automatically receive updates.

Thank you for your patience and understanding! The more information we are able to gather, the better our chances that our engineers will be able to track down and resolve this.

0 comments

Please sign in to leave a comment.