-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oops, it looks like something went wrong. Click OK to automatically reload Skype for Web. #8
Comments
Yeah. Duplicate of #7 Unfortunately I cannot reproduce it and it seems to occur due to some weird logic of Skype for some users. And unfortunately most likely I cannot fix it by this extension. I will also try to update user agent to simulate latest chrome. Maybe there is logic related to it. |
@skliarie also try to disable Maybe this is a reason. FF blocks them for some reason on your env. If this helps you can keep this option disabled (but this very unsafe), or you can use extension Laboratory (Content Security Policy / CSP Toolkit) which can disable CSP for exact site (I didn't tried it by myself, so not sure). |
Hi, I've been getting this error, too, and I use Sidebery so I tried opening Web Skype in a different container from usual but still in the same window, and... the error did not pop up! Not sure if this info will help pinpoint what is going on, but thought I would share in case it helps. |
I have never used this extension, but simply the user-agent switcher which worked fine until recently, when I started seeing the Oops message. I managed to solve the problem. Steps:
Everything works smoothly so far. After logging in to Skype, there's cookies from these domains:
Hope it helps... |
@drougas thank you for the info! I also updated the extension to include those URLs - v0.6.0 |
Tried below, nothing helped:
|
I found some caching issue specific to FF 83, seems to be related: |
It seems to be already fixed in 84. Try to install 84 nightly version and check. |
Sorry, I had missed some details. I had cleaned, cookies, cache, offline website data and active logins in step 1... |
firefox 84 resolved the problem, closing |
Just commenting here because it may help someone. I was still getting "Oops" message and being denied to access Skype Web. After detailed tests, I found out it's because of Instead, we should use P.S.: I only spoof UA for skype.com, I don't think it's needed for any other domain like live.com, live.net, microsoft.com, microsoftonline.com and skypeassets.com. |
I can confirm that this is still an issue. It appears within seconds of loading web skype. You can't do anything because the error message steals all the mouse and keyboard focus. You have to click okay, which reloads the link. You log back in and it's okay for 2 maybe 3 minutes and then the error re-appears. Skype is completely unusable in this state, is there anything anyone can do to fix it? |
Just to add something here, this has started happening suddenly over the last 5-6 days, and it's happening relentlessly and constantly, it's not working at all. |
Yes, I have been having this issue for the past few weeks. Its not working at all because of this message and the reloading |
This is still going on, it's also going wrong in Chromium too. |
I've never used this extension, have been using Web Skype on Chrome/Chromium for a while, no less than a year or two. The last couple of weeks i've had this exact issue frequently. Today has been pretty bad, i've had this happen 5 times this morning. So i bet it's something not directly related to the extension or even Firefox, but it's a problem on Skype Web itself. |
Anyways, cannot reproduce so far... |
I think this is a serious problem with Skype. |
Started getting the "Oops, it looks like something went wrong. Click OK to automatically reload Skype for Web." error, shows up after 1-60 seconds of opening the www.skype.com
tried to clean up cache
Not sure whether it triggered by M$ of my recent firefox upgrade to 83.0 (64-bit) (Ubuntu 20.04)
On my home computer, same setup, the problem does not occur..

The text was updated successfully, but these errors were encountered: