Ticket: "Facebook/LinkedIn: URI Redirect & Access Issues"
@Big Bird Just created a ticket
Question: I am facing too key issues with my deployment. 1. Facebook: Requesting Advanced Access 2. Facebook and LinkedIn: URI Redirect Errors
Attempted: I will follow up with the detail, as I am also getting an error simply trying to submit this form.
Working On: I will follow up with the detail, as I am also getting an error simply trying to submit this form.
Take it from here @Mod 🔥
Question: I am facing too key issues with my deployment. 1. Facebook: Requesting Advanced Access 2. Facebook and LinkedIn: URI Redirect Errors
Attempted: I will follow up with the detail, as I am also getting an error simply trying to submit this form.
Working On: I will follow up with the detail, as I am also getting an error simply trying to submit this form.
Take it from here @Mod 🔥
2 Replies
Multiple Issues Adding Channels: Facebook and LinkedIn
I am facing two one key issues with my deployment.
1. Facebook: Requesting Advanced Access
2. Facebook and LinkedIn: URI Redirect Errors
My deployment is via docker. I have provided my docker compose config at the base of this ticket.
1. Facebook: Requesting Advanced Access
For the majority of permission I need to request advanced access, however most of them are greyed out and say
I assumed that by attempting to add Facebook as a channel from within Postiz that this would make an API call, and thus after waiting 24 hours, these boxes would become available for me to request, but that has not happened. My question therefore is: **What do I need to do to satisfy the requirement to make a successful test API call?
2. Facebook and LinkedIn: URI Redirect Errors
With LinkedIn I get this error:
To request advanced access to this permission, you need to make a successful test API call. It may take up to 24 hours after the first API call for this button to become active.
The redirect_uri does not match the registered value
With Facebook I get this error: URL blocked: This redirect failed because the redirect URI is not white-listed in the app's client OAuth settings. Make sure that the client and web OAuth logins are on and add all your app domains as valid OAuth redirect URIs.
I have tried using the following URIs:
LinkedIn:
http://localhost:4200/integrations/social/linkedin
http://postiz.my.domain:4200/integrations/social/linkedin
https://postiz.my.domain:4200/integrations/social/linkedin
Facebook:
http://localhost:4200/integrations/social/facebook
http://postiz.my.domain:4200/integrations/social/facebook
https://postiz.my.domain:4200/integrations/social/facebook
I use Nginx Proxy Manager and have the IP of my Postiz deployment pointed to postiz.my.domain.
My docker compose:
I have also now tried using port 5000 in my URI
SOLVED
I don't know what I did to solve the API request issue.
Regarding URIs: removing the port number from the URI and using the following worked:
https://postiz.my.domain/integrations/social/linkedin
https://postiz.my.domain/integrations/social/linkedin-page
https://postiz.my.domain/integrations/social/facebookHi @Big Bird Please select an action
The thread is now closed