-
Notifications
You must be signed in to change notification settings - Fork 505
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
Not working on Ngrok free account? #18
Comments
Hi! Recently I had this same issue, I ended up leaving Ngrok. I recommend you to use Serveo instead. If serveo for some reason isn't available please try localhost.run Greetings :) |
Nice service! |
@DanielGarciaCol I set up the serveo and localhose but for some reason my Flask server doesn't seem to catch any requests... I'm not sure what I'm doing wrong |
Hey @EdEn-D ! Try checking the ports. When you start the tunnel, you get a URL that changes every time you open a new tunnel. This means you need to update your webhook URL in Meta's developer portal. Also, don’t forget to update your environment variables accordingly. |
@DanielGarciaCol If you mean update the .env I did. And I got the changing URL.. but still, I get no connections from that URL provided by either serveo or localhost.run on my flask server when accessing it myself through the browser or when trying to verify. Tried several ports. There is something I seem to be missing to make the connection between the serveo/localhost.run domain and my flask server Edit: just did it :'D I'm so happy I'm gonna cry after 3rd day of debugging I just need to 'sudo ufw allow ssh' |
@DanielGarciaCol serveo seems to be down today, following the same process with localhost.run also left me not being able to verify :( . Any idea why this could be? I authenticated my user with localhost.run with SSH, no luck |
Can anyone confirm that they got this to work with an Ngrok free account?
My suspicion is that due to the browser warning that comes up with the free account, meta is not able to verify and this step fails... Trying other methods, will update.
The text was updated successfully, but these errors were encountered: