-
Notifications
You must be signed in to change notification settings - Fork 8
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
Issue: Getting oAuth Invalid Redirect URL error when trying to authorize #11
Comments
What do you have as your baseUrl?
…On Fri, 10 Jul 2020 at 08:13, brianrivet ***@***.***> wrote:
Hi,
I'm using Craftagram 1.1.0 on Craft 3.4.27. I have set up the Instagram
feed as an app in Facebook per the instructions in the readme, but when I
try to authorize in Craft I'm getting an error saying my redirect URL is
invalid. I've double-checked it and it is set up according to the
instructions. Can you please help me to resolve this issue?
Thanks!
Brian
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#11>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAM5Z3N2PPCUVR5JQA4N3OTR225RRANCNFSM4OWJ7F4A>
.
|
My site is https://www.drinkmyhy.com. The redirect URL is set to: https://www.drinkmyhy.com/actions/craftagram/default/auth |
Nevermind. My base url in the CP had a trailing slash. I've resolved the problem. Thanks for the fast response! |
Thanks @brianrivet. I had thought I fixed this in the latest release but apparently not! I'll take another look. |
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I'm using Craftagram 1.1.0 on Craft 3.4.27. I have set up the Instagram feed as an app in Facebook per the instructions in the readme, but when I try to authorize in Craft I'm getting an error saying my redirect URL is invalid. I've double-checked it and it is set up according to the instructions. Can you please help me to resolve this issue?
Thanks!
Brian
The text was updated successfully, but these errors were encountered: