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

sensenet.ru giving 500 error #215

Open
jmez11 opened this issue Nov 9, 2023 · 4 comments
Open

sensenet.ru giving 500 error #215

jmez11 opened this issue Nov 9, 2023 · 4 comments

Comments

@jmez11
Copy link

jmez11 commented Nov 9, 2023

In attempting to set up my frame again (sd card died) i get to the authorization part and see:

This page isn’t working
photoframe.sensenet.nu is currently unable to handle this request.
HTTP ERROR 500

I've disabled ad blockers and tried other browsers. My previously set up and working credential json was what i used. I tried resetting up the credentials from scratch, just to be sure and those failed too.

Any help would be appreciated!

@mrworf
Copy link
Owner

mrworf commented Nov 10, 2023

Odd, I just tried calling https://photoframe.sensenet.nu/photoframe/?register=10.0.0.1:80 from my mobile device (without wifi) to make sure I get the same flow and it works (returns a hash). Can you try the link above and see what you get? Also, just https://photoframe.sensenet.nu should redirect to this github project.

@jmez11
Copy link
Author

jmez11 commented Nov 10, 2023

That doesn't look like the url that my authorize button uses. I see the URL like:

https://photoframe.sensenet.nu/?state=xxx&code=xxx&scope=https://www.googleapis.com/auth/photoslibrary.readonly

@mrworf
Copy link
Owner

mrworf commented Nov 10, 2023

That's the correct URL, the browser calls my link first to get the state value (the hash value). See https://github.com/mrworf/photoframe#how-come-you-contact-photoframesensenetnu- for details on how this flow works.

Reason I posted the link was to make sure you could access the site to get the hash in the first place.

@jmez11
Copy link
Author

jmez11 commented Nov 12, 2023

Yeah, no problems with the first url. The 500 error happens with the redirect url. I'm able to work around it by manually redirecting myself, so ongoing access is not an issue. It's only when setting up the new source. Can you try the full flow by authorizing a new google photos source yourself? It's still failing when i try adding and authorizing.

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

2 participants