-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
cannot do verification on self hosted docker #156
Comments
Hi, I hope that helps. |
i tried, and http://demo.mcaptcha.org/api/v1/pow/siteverify did the trick. |
and i opened the api doc of my own host. there's no such api like /api/v1/pow/ exists. |
The API doc is outdated, |
i follow the README of this git. and it goes fine. i can do registration and create sitekey. and i can integrate the widget to other sites. i barely can do coding. i just follow the guide from chatgpt. thank you |
That's alright, can you please tell me which language you are trying to code in? We have exapmles for Python, JavaScript and Rust. Maybe those will be of help? |
frontend is vue and backend is go. |
That's right, B's backend must do the do a POST request to |
sure.
|
and the frontend part is as below: |
I assume "something" in the client code is replaced with the sitekey? I have no idea what is going on. There's a Go server-side library that does the validation, maybe that'll help. |
ah, yes. it's a long text, so i replaced it with something. |
i self-hosted the mcaptcha docker. and i can access it normally and can make the widget integreated into my forms.
but according to the docs of the backend settings.
1payload = { 2 "token": mcaptcha_token, 3 "key": mcaptcha_sitekey, # captcha site key 4 # mCaptcha account secret; available in settings 5 "secret": mcaptcha_account_secret, 6} 7resp = requests.post( 8 "https://demo.mcaptha.org/api/v1/pow/siteverify", json=payload 9) 10resp = resp.json()
the "https://demo.mcaptha.org/api/v1/pow/siteverify" part. when i replace my own host. it reports 404. and i try to open https://my-own-host/api/v1/pow/siteverify, still 404.
so...how can i solve this situation.
thank you.
The text was updated successfully, but these errors were encountered: