Skip to content

Commit

Permalink
Update faq.md
Browse files Browse the repository at this point in the history
  • Loading branch information
rowlandm authored Mar 12, 2024
1 parent f173e09 commit 362f288
Showing 1 changed file with 5 additions and 2 deletions.
7 changes: 5 additions & 2 deletions faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -119,12 +119,15 @@ RCP also has [a drop-in session that you can go to ask technical questions](http

Make sure you use "Any Availability Zone" if you are using Nectar as some of the University of Melbourne hosts are full.

Make sure you enable 22 SSH access with 0.0.0.0/0 using CIRS. See [the Nectar SSH troubleshooting guide](https://support.ehelp.edu.au/support/solutions/articles/6000149723-troubleshooting-ssh-access-to-a-nectar-instance).

It is recommended to use NeCTAR Ubuntu 22.04 LTS (Jammy) amd64 so that students can share documentation between projects and intakes.

Make sure you enable 22 SSH access with 0.0.0.0/0 using CIRS. See [the Nectar SSH troubleshooting guide](https://support.ehelp.edu.au/support/solutions/articles/6000149723-troubleshooting-ssh-access-to-a-nectar-instance).

If you want to run a web server, it is recommended to use SSL and therefore you will need to enable 443 HTTPS access with 0.0.0.0/0 using CIRS. See [the Nectar SSH troubleshooting guide](https://support.ehelp.edu.au/support/solutions/articles/6000149723-troubleshooting-ssh-access-to-a-nectar-instance).

If you want to run a flask development server, it is recommended to use SSL and therefore you will need to enable port 5000 access with 0.0.0.0/0 using CIRS. For other non-standard ports you will have to do a similar setup. See [the Nectar SSH troubleshooting guide](https://support.ehelp.edu.au/support/solutions/articles/6000149723-troubleshooting-ssh-access-to-a-nectar-instance).


We should also have a standard to setup a SSL web certificate in the future.

## Is it OK for me to post on social media?
Expand Down

0 comments on commit 362f288

Please sign in to comment.