session expires immediately upon login
Closed this issue · 10 comments
dmd commented
Configured using configure-basic.sh. I log in using admin/admin, and immediately am logged out.
Logging back in immediately just logs me out again.
tclose commented
Interesting, that could be a bug related to the timezone.
Which timezone have you configured it for (maybe just send me the whole
config file)? Could you try Australia/Melbourne and see if it works?
…On Fri, 21 Feb 2020 at 07:18, Daniel M. Drucker ***@***.***> wrote:
Configured using configure-basic.sh. I log in using admin/admin, and
*immediately* am logged out.
[image: image]
<https://user-images.githubusercontent.com/41439/74975005-3f755080-53f4-11ea-991a-712e70ddf80b.png>
[image: image]
<https://user-images.githubusercontent.com/41439/74974989-397f6f80-53f4-11ea-9d86-29bb2a2ecea7.png>
Logging back in immediately just logs me out again.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#18?email_source=notifications&email_token=AAIBRFQGCVXNIYHWFGXZVIDRD3QSVA5CNFSM4KYWGPL2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IPDKKFA>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIBRFS6Z5GU4PHQNHTRU4TRD3QSVANCNFSM4KYWGPLQ>
.
--
*THOMAS G. CLOSE, PHD*
Imaging Informatics Officer
*Monash Biomedical Imaging*
Monash University
Room 139, 770 Blackburn Rd
Clayton Campus, Clayton VIC 3800
Australia
T: +61 3 9902 9804
M: +61 491 141 390
E: tom.close@monash.edu
mbi.monash.edu.au
dmd commented
Aha. Changing TIMEZONE to America/New_York in docker-compose.yml fixes this.
dmd commented
Hmm, actually, no, it doesn't. If I stop the container and start it again, I start getting the same problem again!
dmd commented
The only change I made to any file was :%s,Australia/Melbourne,America/New_York,g in docker-compose.yml
dmd commented
I've tried (from scratch) with both configure.sh and configure-basic, and can't get logged in for more than a second without being immediately logged out.
On top of that, it looks like configure.sh isn't exposing 80/443, only 8081, when I run it.
tclose commented
Have you destroyed the containers using docker-compose down? Had I left
hard-coded timezones in the compose file? Sorry about that.
The configure scripts don’t expose any ports (do you mean on your machine’s
firewall?), this needs to be done manually.
On Sat, 22 Feb 2020 at 5:29 am, Daniel M. Drucker ***@***.***> wrote:
I've tried (from scratch) with both configure.sh and configure-basic, and
can't get logged in for more than a second without being immediately logged
out.
On top of that, it looks like configure.sh isn't exposing 80/443, only
8081, when I run it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#18?email_source=notifications&email_token=AAIBRFRSGEULVC6BRCXAVHDREAMQFA5CNFSM4KYWGPL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMTUSAQ#issuecomment-589777154>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIBRFUBJMA4KSWA4CJWQBLREAMQFANCNFSM4KYWGPLQ>
.
--
*THOMAS G. CLOSE, PHD*
Imaging Informatics Officer
*Monash Biomedical Imaging*
Monash University
Room 139, 770 Blackburn Rd
Clayton Campus, Clayton VIC 3800
Australia
T: +61 3 9902 9804
M: +61 491 141 390
E: tom.close@monash.edu
mbi.monash.edu.au
tclose commented
You may need to rebuild with docker-compose build as well
On Sat, 22 Feb 2020 at 8:03 am, Thomas Close ***@***.***> wrote:
Have you destroyed the containers using docker-compose down? Had I left
hard-coded timezones in the compose file? Sorry about that.
The configure scripts don’t expose any ports (do you mean on your
machine’s firewall?), this needs to be done manually.
On Sat, 22 Feb 2020 at 5:29 am, Daniel M. Drucker <
***@***.***> wrote:
> I've tried (from scratch) with both configure.sh and configure-basic, and
> can't get logged in for more than a second without being immediately logged
> out.
>
> On top of that, it looks like configure.sh isn't exposing 80/443, only
> 8081, when I run it.
>
> —
> You are receiving this because you commented.
>
>
> Reply to this email directly, view it on GitHub
> <#18?email_source=notifications&email_token=AAIBRFRSGEULVC6BRCXAVHDREAMQFA5CNFSM4KYWGPL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMTUSAQ#issuecomment-589777154>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAIBRFUBJMA4KSWA4CJWQBLREAMQFANCNFSM4KYWGPLQ>
> .
>
--
*THOMAS G. CLOSE, PHD*
Imaging Informatics Officer
*Monash Biomedical Imaging*
Monash University
Room 139, 770 Blackburn Rd
Clayton Campus, Clayton VIC 3800
Australia
T: +61 3 9902 9804
M: +61 491 141 390
E: ***@***.***
mbi.monash.edu.au
--
*THOMAS G. CLOSE, PHD*
Imaging Informatics Officer
*Monash Biomedical Imaging*
Monash University
Room 139, 770 Blackburn Rd
Clayton Campus, Clayton VIC 3800
Australia
T: +61 3 9902 9804
M: +61 491 141 390
E: tom.close@monash.edu
mbi.monash.edu.au
dmd commented
Rebuilding doesn't help either.
tclose commented
Could you jump into each container and see what the time is? I.e something
like
docker-compose -f docker-compose.yml exec xnat-web date
On Wed, 26 Feb 2020 at 8:11 am, Daniel M. Drucker ***@***.***> wrote:
Rebuilding doesn't help either.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#18?email_source=notifications&email_token=AAIBRFQ4EO7XEF3PW4EEYSDREWCPRA5CNFSM4KYWGPL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEM5QO7Q#issuecomment-591071102>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIBRFSUOOBDB4TXMD7V6DTREWCPRANCNFSM4KYWGPLQ>
.
--
*THOMAS G. CLOSE, PHD*
Imaging Informatics Officer
*Monash Biomedical Imaging*
Monash University
Room 139, 770 Blackburn Rd
Clayton Campus, Clayton VIC 3800
Australia
T: +61 3 9902 9804
M: +61 491 141 390
E: tom.close@monash.edu
mbi.monash.edu.au
dmd commented
arrrg Sorry again. Mea culpa. This was due to me having rolled back the VM I've been experimenting with this in, and not realizing that it takes a while for ntpd to fix the time.