Bug #776
closedUsers are unable to register to projects.duckcorp.org
100%
Description
There is an issue related to the captcha:
Oops, we failed to validate your reCAPTCHA response. Please try again.
I tried with firefox and chromium.
/var/log/redmine/dc/production.log
from the redmine
LXC container:
Started POST "/account/register" for 185.238.6.46 at 2022-07-10 12:53:52 +0000 Processing by AccountController#register as HTML Parameters: {"utf8"=>"✓", "authenticity_token"=>"[REDACTED]", "user"=>{"login"=>"pilou_test", "password"=>"[FILTERED]", "password_confirmation"=>"[FILTERED]", "firstname"=>"pilou", "lastname"=>"pilou_test", "mail"=>"pilou_test@ir5.eu", "language"=>"fr"}, "g-recaptcha-response"=>"[REDACTED]", "commit"=>"Soumettre"} Current user: anonymous Rendering plugins/recaptcha/app/views/account/register.html.erb within layouts/base Rendered plugins/recaptcha/app/views/account/register.html.erb within layouts/base (8.8ms) Completed 200 OK in 3022ms (Views: 14.7ms | ActiveRecord: 1.4ms)
Updated by Pierre-Louis Bonicoli over 2 years ago
- Related to Bug #718: redmine: unable to register a new account added
Updated by Pierre-Louis Bonicoli over 2 years ago
@Marc Dequènes : could you check if there an issue (or a message) with your google account (because the recaptcha key is linked to your account)?
Updated by Pierre-Louis Bonicoli over 2 years ago
Pierre-Louis Bonicoli wrote:
@Marc Dequènes : could you check if there an issue (or a message) with your google account (because the recaptcha key is linked to your account)?
This isn't needed :)
It looks like the redmine
container isn't allowed/able to access to internet:
# curl --connect-timeout 2 https://www.google.com/recaptcha/api/siteverify curl: (28) Failed to connect to www.google.com port 443: Connection timed out
Updated by Pierre-Louis Bonicoli over 2 years ago
- Branch set to  fix-lxc-redmine-network
Check fix-lxc-redmine-network
for a proposed fix.
Another way would be to use the ppp-network
. In order to do that, I guess TABLE_out_hivane_SUBNET_IP4
in /etc/network/multihoming
should be updated?
Updated by Marc Dequènes over 2 years ago
Sorry, totally failed to check this, will have a look. Thanks for investigating.
Updated by Marc Dequènes over 1 year ago
Thanks pilou again and really sorry for the lag.
While updating the firewalling rules I realized I was breaking something… Anyway I just changes the multihoming rules and it works again.
Updated by Marc Dequènes over 1 year ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset duckcorp-infra|4296b62608b5a9f17cf324c465f8fdb3a4ed91c8.