Skip to content
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 connect to neurogitea #318

Open
jcohenadad opened this issue May 28, 2024 · 8 comments
Open

Cannot connect to neurogitea #318

jcohenadad opened this issue May 28, 2024 · 8 comments
Assignees

Comments

@jcohenadad
Copy link
Member

i keep having connection issue and i keep forgetting what's the solution so i'm just going to create an issue so i can quickly go back to it everytime i have that problem--

image

@jcohenadad
Copy link
Member Author

❌ Does not work:

julien-macbook:~ $ ssh -N -L 3000:localhost:3000 [email protected]
[email protected]'s password: 
Permission denied, please try again.

@jcohenadad
Copy link
Member Author

jcohenadad commented May 28, 2024

❌ Does not work:

julien-macbook:~ $ ssh -N -L 3000:localhost:3000 [email protected]@data.neuro.polymtl.ca
[email protected]@data.neuro.polymtl.ca's password: 

(keeps hanging)

after reading that it is normal for it to keep hanging, i did what was asked below, but no success

image

i tried with p101317 and wth [email protected]

@namgo
Copy link
Member

namgo commented May 28, 2024

@mguaypaq I remember we had discussed creating a local account for Julien - is this still an option?

@jcohenadad
Copy link
Member Author

because i keep needing the list of datasets (sometimes very urgently for admin/ethics purposes), until this is resolved, i'm just going to list the datasets below:

Terminal output
datasets/basel-mp2rage
datasets/bavaria-quebec-spine-ms
datasets/bavaria-quebec-spine-ms-unstitched
datasets/beijing-tumor
datasets/canproco
datasets/data_axondeepseg_bf_source
datasets/data_axondeepseg_bf_training
datasets/data_axondeepseg_cars
datasets/data_axondeepseg_sickkids
datasets/data_axondeepseg_stanford
datasets/data_axondeepseg_tem
datasets/data_axondeepseg_users
datasets/data_axondeepseg_vcu
datasets/data_axondeepseg_wakehealth_source
datasets/data_axondeepseg_wakehealth_training
datasets/dcm-oklahoma
datasets/dcm-zurich
datasets/dcm-zurich-lesions
datasets/dcm-zurich-lesions-20231115
datasets/eeg-epilepsy
datasets/exvivo-spinal-cord
datasets/gmseg-challenge-2016
datasets/goldatlas
datasets/inspired
datasets/levin-stroke
datasets/lumbar-epfl
datasets/lumbar-nusantara
datasets/lumbar-vanderbilt
datasets/marseille-3t-mp2rage
datasets/marseille-rootlets
datasets/marseille-t2s-template
datasets/mni-bmpd
datasets/model_seg_exvivo_gm-wm_t2_unet2d-multichannel-softseg
datasets/mrspineseg-challenge-2021
datasets/msseg_challenge_2016
datasets/msseg_challenge_2021
datasets/nih-ms-mp2rage
datasets/philadelphia-pediatric
datasets/sci-colorado
datasets/sci-paris
datasets/sci-zurich
datasets/sct-testing-large
datasets/sct-testing-release
datasets/spider-challenge-2023
datasets/synthrad-challenge-2023
datasets/template
datasets/template_dog_virginiatech
datasets/twh-rootlets
datasets/uk-biobank
datasets/uk-biobank-processed
datasets/umass-ms-ge-excite1.5
datasets/umass-ms-ge-hdxt1.5
datasets/umass-ms-ge-pioneer3
datasets/umass-ms-siemens-espree1.5
datasets/uqueensland_mouse
datasets/whole-spine
datasets/zurich-mouse

@nullnik-0
Copy link

I remember we had discussed creating a local account for Julien - is this still an option?

Yes, I did this a while ago. I'm just trying to find the issue where I left the instructions!

@nullnik-0
Copy link

this is the issue

@jcohenadad do you still have the credentials that I sent you?

@jcohenadad
Copy link
Member Author

@jcohenadad do you still have the credentials that I sent you?

yes-- sorry, i had forgotten-- i was able to log in with it-- i hope the issue with my username will be fixed at some point

@nullnik-0
Copy link

Some updates:

  • It looks like upstream has finally added julien to neuropoly (GE) and removed him from GRAMES.
  • This means that using [email protected] should, in theory no longer be necessary with this account.
  • Except that I checked the auth logs on data and Julien seems to be authenticating successfully with [email protected], which doesn't make much sense
  • @namgo and I talked about this in our meeting, and he is going to look into this more!
  • Good news is that upstream opened port 80 for us, so the port forwarding command should no longer be needed, and you should be able to connect to the site as normal while on the VPN.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants