Invalid form authenticity token error #555
Comments
|
Are there any errors in the logs? I usually only see that error if you try
to login without refreshing the page after a container/server restart.
…On Sun, Apr 21, 2024, 8:01 AM Mikolaj98p ***@***.***> wrote:
Hello,
On fresh install on my qnap i have error on login: Invalid form
authenticity token error.
Hardware: Qnap TS-431P
Soft generated from tag: 5.1.2-1
Inspect from docker Config.Env:
"REDMINE_HTTPS=true"
"GEM_HOME=/usr/local/bundle"
"RAILS_ENV=production"
"REDMINE_LOG_DIR=/var/log/redmine"
"RUBY_DOWNLOAD_URL=https://cache.ruby-lang.org/pub/ruby/3.2/ruby-3.2.3.tar.xz"
"DB_HOST=<HIDDEN>"
"DB_PASS=<HIDDEN>"
"DB_NAME=redmine_production"
"BUNDLE_SILENCE_ROOT_WARNING=1"
"REDMINE_ASSETS_DIR=/etc/docker-redmine"
"REDMINE_INSTALL_DIR=/home/redmine/redmine"
"RUBY_VERSION=3.2"
"DB_ENCODING=utf8"
"REDMINE_BUILD_ASSETS_DIR=/etc/docker-redmine/build"
"REDMINE_RUNTIME_ASSETS_DIR=/etc/docker-redmine/runtime"
"REDMINE_USER=redmine"
"REDMINE_VERSION=5.1.2"
"DB_USER=redmine"
"BUNDLE_APP_CONFIG=/usr/local/bundle"
"LANG=C.UTF-8"
"PATH=/usr/local/bundle/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
"REDMINE_DATA_DIR=/home/redmine/data"
"REDMINE_HOME=/home/redmine"
"RUBY_DOWNLOAD_SHA256=cfb231954b8c241043a538a4c682a1cca0b2016d835fee0b9e4a0be3ceba476b"
"DB_ADAPTER=mysql2"
—
Reply to this email directly, view it on GitHub
<#555>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABK2RGPEL6WAVPHPJZM4H6DY6P5GVAVCNFSM6AAAAABGRR32T2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGI2TKMJZGYYTEMQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
Okay looks like your browser did fetch a fresh copy of the login page and
then sent the login details.
However the server responded with the following...
Can't verify CSRF token authenticity.
Did older versions of the image work? I suspect this is not a version issue
and has something to do with your setup.
…On Sun, Apr 21, 2024, 8:14 AM Mikolaj98p ***@***.***> wrote:
production.log
<https://github.com/sameersbn/docker-redmine/files/15053013/production.log>
—
Reply to this email directly, view it on GitHub
<#555 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABK2RGOQLWIOQEHLWNXUIG3Y6P6YFAVCNFSM6AAAAABGRR32T2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRYGE2TGNRXGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Oryginal from https://hub.docker.com/_/redmine/ works fine but without ssl. |
|
Can you verify your ssl cert is working? I saw one post where someone had a
broken ssl connection and got the same error. Maybe test with out https
first.
…On Sun, Apr 21, 2024, 9:42 AM Mikolaj98p ***@***.***> wrote:
Okay looks like your browser did fetch a fresh copy of the login page and
then sent the login details. However the server responded with the
following... Can't verify CSRF token authenticity. Did older versions of
the image work? I suspect this is not a version issue and has something to
do with your setup.
… <#m_270046393118035021_>
On Sun, Apr 21, 2024, 8:14 AM Mikolaj98p *@*.*> wrote: production.log
https://github.com/sameersbn/docker-redmine/files/15053013/production.log
<https://github.com/sameersbn/docker-redmine/files/15053013/production.log>
— Reply to this email directly, view it on GitHub <#555 (comment)
<#555 (comment)>>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABK2RGOQLWIOQEHLWNXUIG3Y6P6YFAVCNFSM6AAAAABGRR32T2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRYGE2TGNRXGA
<https://github.com/notifications/unsubscribe-auth/ABK2RGOQLWIOQEHLWNXUIG3Y6P6YFAVCNFSM6AAAAABGRR32T2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRYGE2TGNRXGA>
. You are receiving this because you commented.Message ID: @.*>
Oryginal from https://hub.docker.com/_/redmine/ works fine but without
ssl.
—
Reply to this email directly, view it on GitHub
<#555 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABK2RGPVBRNO4CFM6XAKGGTY6QJEFAVCNFSM6AAAAABGRR32T2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRYGE3TONJTGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Without ssl working. |
|
I changed certificate from oryginal from qnap to generated via openssl command and working. |
|
I've no idea. Though i don't see why not.
…On Wed, Apr 24, 2024, 12:07 PM Mikolaj98p ***@***.***> wrote:
I changed certificate from oryginal from qnap to generated via openssl
command and working.
Can I use Lets encrypt certs from qnap?
—
Reply to this email directly, view it on GitHub
<#555 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABK2RGN327RLWQ6T3YSY5ALY677IVAVCNFSM6AAAAABGRR32T2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZVGY2DOOBUG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
At first time I used certs from my qnap, but login page returned error in that issue, generated self signed working. |
|
I dont know. I dont think a qnap cert would be any different then any other
cert.
…On Thu, Apr 25, 2024, 11:32 AM Mikolaj98p ***@***.***> wrote:
At first time I used certs from my qnap, but login page returned error in
that issue, generated self signed working.
How I can apply qnap lets encrypt certs?
—
Reply to this email directly, view it on GitHub
<#555 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABK2RGNYWR6C23FKTOHUBZTY7EOZPAVCNFSM6AAAAABGRR32T2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZXGU4DKNZYGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Ok, qnap update helped. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
On fresh install on my qnap i have error on login:
Invalid form authenticity token error.Hardware: Qnap TS-431P
Soft generated from tag:
5.1.2-1Inspect from docker
Config.Env:The text was updated successfully, but these errors were encountered: