Whenever I click on a discussion on the forum I get the error message with a red background "Oops! Something went wrong during a cross-origin request. Please reload the page and try again." If I reload the page and try again the same thing happens.
This is happening on Firefox and Brave browsers but seems OK on Chrome, Opera and Edge. I normally use Firefox but I am having to use Chrome to send this message. I have tried clearing the cache on my Firefox and Brave browsers.

    Rikki Hm interesting, I am writing this from FF and it seems to work. When you say an error happens when you click on a discussion, do you mean click on some forum thread (like this one)?

      Hi,

      The same thing happens here when I use MS Edge. Firefox and Chrome the two other browsers I use seem to work fine. I can not reproduce the "Oops! Something went wrong during a cross-origin request" error in Chrome and Firefox. It happens me when I click on one of the forum threads like this one. while using MS Edge

      *** Just tested some more with Edge and found out that refreshing the page (F5) enables me to read and reply to the thread. Going to another thread though makes the error re-appear. Logging out and in again solves this for one session. Closing the website tab and opening a new one however reproduces the same problem in Edge.

      Peter

      Hi, Peter,
      the same happens with my browser too (MS Edge), ... could be an "Edge" setting problem, but I didn't find yet any settings which could be a possible cause.
      Klaus

      Hm, writing this from Edge and it seems to work ok... We are talking about Edge for Windows, right?

      StylePlayer Actually it was happening when I clicked on anything and even just scrolling down the page, But I have just logged out of the forum and logged back in and it seems to work OK now - at least for the moment!

      Hi StylePlayer,

      Yes, I am using Windows 11 and latest version of MS Edge. Log out and in again so far is the only option that works. I tried logging out before closing the website and browser and start the browser again and let the browser log in automatically (Remember me option) or manually log in. But then the “oops” errors are back. Going to this website and do a log out and log in is the only thing that gets rid of the problem for one session. I could use chrome or firefox since these browsers work fine and do not seem to have this problem but since I have really bad eyesight andt Edge has a great feature called read out loud (with natural voices) Edge is my goto browser for news sites and forums.

      hope it helps pinpointing the problem,
      Peter

        XnX Thank you for extra details, I will try to poke around some more. So simply refreshing the forum page doesn't solve the problem, right?
        I saw this "oops" error once but then after refreshing the page it went away, I wish I had some reliable way to reproduce the problem. It could be also that the site is more overloaded during the day in EU and I suspect this what might be causing it, and when I look at it during EU night the problem is not there. Do you see this problem reliably around the clock?

        • XnX replied to this.

          StylePlayer After refreshing the post becomes visible es but the erros stays even when you click them away thet return on screen. I will let you know after I've tested this during nighttime and very early morning.

          Peter175

          Just to let you know this is still happening in Firefox (version 130.0.1) making the forum almost unusable for me. I did a test earlier as follows:
          Go to styleplayer.io
          Log in
          Select Community - opens Welcome page - defaults to All discussions
          Click on Support - 2 error messages - Oops! Something went wrong during a cross-origin request. Please reload the page and try again.
          Reload page - error gone - displays Support discussions
          Click on a discussion - error appears - discussion doesn't load - displays spinning loading thing
          Reload the page - discussion displays and error appears.

          I tried viewing the forum in logged out status. Initially it worked then the errors started again so it doesn't seem to matter if I am logged in or not.

          I have tried loading Firefox in safe mode but the errors still appear, suggesting it is a server side issue.

          I also checked the browser console and these are the full errors I am getting:

          Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://styleplayer.io/community/assets/fonts/fa-regular-400.ttf. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 200.

          downloadable font: download failed (font-family: "Font Awesome 5 Free" style:normal weight:400 stretch:100 src index:3): bad URI or cross-site access not allowed source: https://styleplayer.io/community/assets/fonts/fa-regular-400.ttf
          Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://styleplayer.io/community/assets/fonts/fa-solid-900.ttf. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 200.

          downloadable font: download failed (font-family: "Font Awesome 5 Free" style:normal weight:900 stretch:100 src index:3): bad URI or cross-site access not allowed source: https://styleplayer.io/community/assets/fonts/fa-solid-900.ttf

          I don't know if all this is of any help but it seems to be a CORS problem related to downloadable fonts.

            Rikki Thank you this is super useful! But also super puzzling 😢

            This error occurs when you try to load some resource from an unrelated domain, but all the listed resources are from this domain.

            Seeing that you are the only one seeing these CORS errors make me think you have some very agressive antivirus or VPN or proxy that reroutes all the traffic through it's own domain or something. Can you think of anything like that that you might have?

            If possible, would you be able to make a screenshot of these error messages inside a console and send it to contact@styleplayer.io

            Thank you.

              StylePlayer Hi again. I tried to replicate the error this morning but the site was working well. However your reference to antivirus and VPN got me thinking. I use a VPN quite often as I live in Portugal and often need to connect to sites in the UK and a few other European countries via a VPN (Nord in my case). So I tested it with my VPN on and yes, it produced the error. I switched the VPN off but the error continued until I cleared the browser cache and restarted Firefox.

              So I tried again with the VPN connected to the UK and there was no error this time. Then I tried connecting the VPN to a server as far away as possible - New Zealand - and the error came back.

              It all seemed a bit random but I do know that from time to time a the VPN can slightly slow down my internet connection. I I noticed that when I first load the forum page it sometimes takes a moment to display the list of discussions. If that delay becomes a little longer - maybe half a second or so - I see the spinning thingy (I think it's called a throbber) and then the error displays.

              So it could be that viewing the site via a VPN potentially causes a timeout. I don't know if it's possible but maybe there is a configuration setting somewhere in the forum software to increase the timeout by, let's say, 500 milliseconds, which might avoid similar issues for users in the future.

              I am sending a screen shot of the error via the contact form.

              Great site by the way. I think the arranger community has been crying out for something like this for years.

                Rikki I see, yeah that's probably what it is. Normally VPN would be fully transparent and shouldn't interfere with the requests, I suspect in this case they are doing something funky trying to cache some resources to save on traffic, so they reroute the requests to their cache servers and the browser blocks them because it looks suspicious that they are coming from a different domain. Our servers are hosted in the US, so if you can choose US VPN that should work the fastest.
                If it shows you CORS errors it shouldn't be related to a timeout, it's a domain discrepancy issue. I can try disabling this CORS check on our domain, will let you know once done.

                Thank you.