Skip to content
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

Worker not working getting 301. #171

Open
ATOM49 opened this issue Jan 16, 2022 · 5 comments
Open

Worker not working getting 301. #171

ATOM49 opened this issue Jan 16, 2022 · 5 comments

Comments

@ATOM49
Copy link

ATOM49 commented Jan 16, 2022

In Preview:
Mismatch between origin and baseUrl (dev).
image

In HTTP:
301 Moved Permanently
image

Followed the exact steps as mentioned in Fruition Website

@tamagamis
Copy link

Hi there @ATOM49 , I see that error sometimes "almost always comes out error there" to prove that the script works clear browser cache, cloudflare cache, dns and enter private mode to your domain and verify.

why do you have 301 enabled?

Important note: use script from the same "official site" or a script without modification and then make the modifications.

@Brenndoerfer
Copy link

I am actually also getting the same 301 error. Followed all steps, tried multiple domains, played around with cloudflare settings - none resolved it.

@bookingninja
Copy link

bookingninja commented May 10, 2022

Was trying to set up a site today and kept running into this same issue. Took some digging in here, but looks like this was resolved on #140. The solution was to change the domainBaseUrl in the script:
old | window.CONFIG.domainBaseUrl = 'https://${MY_DOMAIN}';
new | window.CONFIG.domainBaseUrl = location.origin;

@piavgh
Copy link

piavgh commented May 28, 2022

Was trying to set up a site today and kept running into this same issue. Took some digging in here, but looks like this was resolved on #140. The solution was to change the domainBaseUrl in the script: old | window.CONFIG.domainBaseUrl = 'https://${MY_DOMAIN}'; new | window.CONFIG.domainBaseUrl = location.origin;

Still can not fix my site, is there any other solution?

@VivienP
Copy link

VivienP commented Feb 6, 2023

@piavgh did you succeed to fix your issue? I have the same problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants