-
I followed the getting started guide to the T. I have an OAuth app correctly configured: I have the site setup on vercel perfectly: https://pgloa-website.vercel.app/ But when I attempt to signin with github at this URL: https://pgloa-website.vercel.app/outstatic I get the following error: Url of that page is: https://pgloa-website.vercel.app/outstatic?error=repository-not-found I followed the troubleshooting guide and am doing everything they say: https://outstatic.com/docs/faqs#troubleshooting-login-and-repository-access-issues I even set the repo public (which im sure I shouldnt need to do): https://github.com/mikecann/pgloa-website Any ideas? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 7 replies
-
Hey @mikecann, Thanks for trying Outstatic! I'm sorry to hear you are having trouble with your install. For your project it should be:
Is that what you have? Let me know. |
Beta Was this translation helpful? Give feedback.
-
Hi Andre,
Good question; I think it needs a single line of text on the FAQs, right
after the part about variables for slug - ‘With all the settings given,
reploy your site to update the changes’ (or, something like that).
Matt
…On Sun, 19 Nov 2023 at 13:41, Andre Vitorio ***@***.***> wrote:
Hey @nmcpmadmin <https://github.com/nmcpmadmin> and @mikecann
<https://github.com/mikecann> ,
Thanks for this feedback.
Where do you think it makes sense for us to add this notice in the docs?
—
Reply to this email directly, view it on GitHub
<#159 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BBLHKD4IWEY22CBWSHTLR3TYFIEADAVCNFSM6AAAAAA7QV4CKOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TMMJRGIYDM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Excellent, Andre - that should help anyone else who encounters that issue.
Have a good week.
Matt
.
…On Mon, 20 Nov 2023 at 09:58, Andre Vitorio ***@***.***> wrote:
Done
<https://outstatic.com/docs/faqs#troubleshooting-login-and-repository-access-issues>!
Thank you for the suggestion.
—
Reply to this email directly, view it on GitHub
<#159 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BBLHKDZTJOOHBDVAL6L7W7LYFMSURAVCNFSM6AAAAAA7QV4CKOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TMMJXGY2TG>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
@avitorio I've had a similar issue in my development environment on Gitpod.io. I commented out all of the settings in .env.local, except for the first 4 settings, restarted the development server and managed to login. The problem is that the redirect sent me back to localhost:3000 instead of to the app URL defined in Github OAuth apps. I guess it must be hardcoded somewhere. The login was successful though, so when I opened the actual /outstatic URL, I was logged in. I have 2 suggestions:
You can try this yourself by adding the following .gitpod.yml file to the root of the blog project and opening the Github repo on Gitpod.io: # List the start up tasks. Learn more https://www.gitpod.io/docs/config-start-tasks/
tasks:
- name: Start development environment
init: npm install
command: npm run dev
# List the ports to expose. Learn more https://www.gitpod.io/docs/config-ports/
ports:
- port: 3000
onOpen: open-preview
description: Website preview Kind regards, |
Beta Was this translation helpful? Give feedback.
I added the
OST_REPO_OWNER
and no change.Then I had a thought overnight, maybe I need to re-deploy on vercel.
I did so and now it works!??
Haha maybe I should have known that, maybe it should be in the docs shrug anyways, at least it works now :) thanks!