Hello, I am trying to connect facebook page and I ...
# ask-community-for-troubleshooting
m
Hello, I am trying to connect facebook page and I am facing this error: HTTPError('400 Client Error: Bad Request for url . Has anyone else faced ? please guide.
m
Hi Muhammad, there is an issue for that already
You can try the URL giving a 400 on the dedicated Facebook tool, but the issue for me was a non existant field being requested.
See attached the fix I made
n
Let me know if Max's comments help, @Muhammad Usman!
m
No @Nataly Merezhuk (Airbyte), the issue is still there 😕 I tried on python it it worked there. but credentials not working on airbyte.
n
That's unfortunate! Then the best thing to do in this case is to monitor the issue: https://github.com/airbytehq/airbyte/issues/9827
I see one of our team members has recently commented: "Hi Folks, thanks for flagging this issue. We are actively monitoring it, but since this is an alpha connector, we are not prioritizing the issue at this time. As always, we welcome contributions from our community to resolve this problem. Thank you!" So if you've got time to contribute, please do so!
l
Hi, any news on this issue? I tried to connect to the Facebook Pages source and I get an error "non-json response"
m
Nothing on my side, we are still relying on old custom docker image within our infrastructure
l
oh, thanks for answering @Max Perdrigeat. Do you remember which modifications you had to do in order to make it work? I´m kind of desperate here
m
Non-json response during setup, I had that one when token was not right Are you using long lived page token ?
l
Yes. Almost sure. I did it through curl
m
Can you put in it Facebook Access Token Debugger tool and paste the results here? Redacting out the personal details of course
l
Hi, That´s the token debugger..
m
Hi, the token type looks good ; but I feel some permission may be missing Try generate a token with ALL permission and try it, if it works reduce permission until you find out the minimum viable ones
l
@Max Perdrigeat thanks for answering. How do I generate with all permissions?
m
Using the Graph API Explorer: • Paste your access token on the top right input box • Select all permissions right below • Click Generate Acces Token • The token has been updated • Check your work with token debugger
l
Hi, I tried it, still same error..
m
As the user on which you generated the token. Does it have all the permissions as well (like revenues and manage page) ?
l
Hi @Max Perdrigeat, I have full access, but still same error 😭
m
I do not know what else could be the problem if your airbyte and connectors are up to the latest version No more logs when trying to setup the connector?
l
no just this.. I went over the documentation and this catch my eye. The page URL is Top-10-XXXXXXX but the page id is just the numbers. When I try to set the page ID as in the documentation as Top-10-XXXXXXX it fails..
Another thing that I see is that in the Graph API explorer, I don't have the "public profile" permission
m
I believe public profile is mandatory, you cannot seem to get.that permission?
l
@Max Perdrigeat, another question, as I still have the same error of no json response. The documentation states that the page ID should be "Test-1111111111". Mine also contains text but if I put that ID I get an error that the page doesn´t exist
m
When you access the URL
<http://www.facebook.com/|www.facebook.com/><Page_ID>
on your browser, does the page exist ?
l
it redirects me to this: https://www.facebook.com/Top-10-111666925186320/ but I can´t create a page access token with the text, just the following id: 111666925186320. I also created the page token through the graph API and also gives me a non json response on airbyte
m
Page id should only contain numbers, in generation and when setting up with Airbyte
l
Yes, but it returns non json response.. that´s part of the debugger..
I´m going crazy
Can someone that manages to use the Facebook Pages source connector tell me which connector version he uses? And what scopes appear in it´s token?
@Max Perdrigeat, hi, as I´m out of ideas of what can be the problem, can you tell me which connector version you are using?
m
Last time we made it work was version
0.1.6
from what I see Since then we put our migration project on hold because of connector instability
l
I´ve opened a github issue, if you want to support it https://github.com/airbytehq/airbyte/issues/24638