From 7d6457bfdddfdcbdf74088d54afa4d46ec2c6d63 Mon Sep 17 00:00:00 2001 From: kei5uke Date: Fri, 2 Oct 2026 13:42:26 +0200 Subject: [PATCH 1/2] fix: prettier issues --- .../components/lab-access/LinuxJourney.vue | 782 ++++-------- .../components/lab-access/MacJourney.vue | 9 +- .../components/lab-access/WindowsJourney.vue | 1079 ++++++----------- 3 files changed, 672 insertions(+), 1198 deletions(-) diff --git a/docs/.vitepress/theme/components/lab-access/LinuxJourney.vue b/docs/.vitepress/theme/components/lab-access/LinuxJourney.vue index 236137f142..6996ffe919 100644 --- a/docs/.vitepress/theme/components/lab-access/LinuxJourney.vue +++ b/docs/.vitepress/theme/components/lab-access/LinuxJourney.vue @@ -1,10 +1,10 @@ - +
  1. Click on the Network Manager icon in the task bar.
  2. Select Edit Connections...
  3. Click Add.
  4. Choose Import a saved VPN configuration and click Create.
    5. -
  5. Select the OpenVPN profile named {{ username }}.ovpn that you collected in Step 1.
    6. +
  6. + Select the OpenVPN profile named {{ username }}.ovpn that you collected in Step 1. +
  7. Enter your user name (same as the OpenVPN profile file name).
  8. Click on the person icon in the Password field and select Ask for this password every time.
  9. Enter the Private Key Password with the VPN passphrase sent to you from HUNT over Signal.
    10. @@ -374,11 +365,7 @@ const openSurvey = () => { - +
    1. Click on the Network Manager icon in the task bar.
      2. @@ -396,17 +383,9 @@ const openSurvey = () => { - + - + @@ -418,23 +397,20 @@ const openSurvey = () => { - +

      # Authenticate VPN

      - If the Authenticate VPN prompt pops up again, then try to log in again with a new verification code. + If the Authenticate VPN prompt pops up again, then try to log in again with a new verification code.

      @@ -450,7 +426,8 @@ const openSurvey = () => {

      # Unable to apply changes

      - If you are unable to click Apply after your changes, try to re-enter your Private Key Password using your VPN passphrase that you received in Signal message. + If you are unable to click Apply after your changes, try to re-enter your Private Key Password using your VPN passphrase that you + received in Signal message.

      @@ -465,56 +442,50 @@ const openSurvey = () => {

      # Could not read Auth error

      - The error messages below indicates that TOTP (Google Auth) code is not accepted. - You should try to setup your TOTP one more time or request a TOTP reset in Service desk. - 
      +                          The error messages below indicates that TOTP (Google Auth) code is not accepted. You should try to setup your TOTP one more time or request a TOTP reset
+                          in Service desk.
+                          
      
+                            
                                   
-                          
      
-
+
      +

      # Could not read Private Key error

      The error messages below indicates that there is a typo in the Private Key Password (step 2.3.5) and you need to type it in again. - 
      +                          
      
+                            
                                   
-                          
      
+
      +
      - 
      +                          
      
+                            
                                   
-                          
      
+
      +

      # Detect firewall blocks

      -
      - If you want to check whether your VPN connection is blocked by the firewall, install nmap using: sudo apt install nmap and then run: -
      - +
      If you want to check whether your VPN connection is blocked by the firewall, install nmap using: sudo apt install nmap and then run:
      +
      If traceroute ends with 129.241.176.121 no blocking was detected. Although if tracing seems stuck send us a screenshot in service desk.
      - + - If nothing works, please head over to our main troubleshooting section for more information on how to troubleshoot connections. + If nothing works, please head over to our main troubleshooting section for more + information on how to troubleshoot connections.       @@ -533,21 +504,12 @@ const openSurvey = () => {

      # {{ passChangeId }}. SSH Passphrase change

      - + Ensure that you are logged into VPN. - - {{ getNextItem(passChangeId, true) }} Design . - - - {{ getNextItem(passChangeId) }} Start Terminal application. - + {{ getNextItem(passChangeId, true) }} Design . + {{ getNextItem(passChangeId) }} Start Terminal application. {{ getNextItem(passChangeId) }} Login to entry machine. { {{ getNextItem(passChangeId) }} You should then be prompted to enter a password. Enter your SSH temporary key from Signal message. - 
      +              
      
+                
                       
-              
      
+
      +
      {{ getNextItem(passChangeId) }} When asked for current UNIX password type in your SSH temporary key from Signal message. - 
      +              
      
+                
                       
-              
      
+
      +
      {{ getNextItem(passChangeId) }} Enter your new passphrase and retype for verification. You will be kicked off the entry machine right after your password is changed. - 
      +              
      
+                
                       
-              
      
-              
+
      +
      + If you are getting an Authentication token manipulation error check strength requirements for passphrase in step {{ passChangeId }}.1.       {{ getNextItem(passChangeId) }} Reconnect to entry using your new passphrase. - + Expected result: - 
      +              
      
+                
                         
-              
      
+
      +
      {{ getNextItem(passChangeId) }} When logged into your entry machine, connect to your home machine. @@ -611,15 +572,19 @@ const openSurvey = () => { - 
      +              
      
+                
                       
-              
      
+
      +
      {{ getNextItem(passChangeId) }} Similar to above, you will be asked for a new password. Type your new passphrase two times. - 
      +              
      
+                
                       
-              
      
+
      +
      {{ getNextItem(sshConfId, true) }} Open new Terminal window (CTRL + ALT + T) and assure SSH Config file exists. No output is expected. - + {{ getNextItem(sshConfId) }} Open SSH Config file. - + {{ getNextItem(sshConfId) }} Replace old lab configuration in SSH Config opened in Text Editor and then save changes. - + {{ getNextItem(sshConfId) }} Add lab configuration into SSH Config opened in Text Editor and then save changes. - + {{ getNextItem(sshConfId) }} Remove old fingerprint. - + {{ getNextItem(sshConfId) }} Test by connecting straight into home machine. - - - - {{ getNextItem(sshConfId) }} Close Terminal window to make sure you are disconnected from your lab. + + {{ getNextItem(sshConfId) }} Close Terminal window to make sure you are disconnected from your lab. Next       @@ -821,76 +724,43 @@ const openSurvey = () => { Let's set up your hosts file on your local computer.
      - This allows you to connect to HUNT Workbench in your lab using a domain name {{ fqdn }}. -

      + This allows you to connect to HUNT Workbench in your lab using a domain name {{ fqdn }}.

      - {{ getNextItem(hostsFileId, true) }} On your local computer, open your /etc/hosts file in your preferred text editor. - You will be asked for administrator password of your local computer. -

      + {{ getNextItem(hostsFileId, true) }} On your local computer, open your /etc/hosts file in your preferred text editor. You will be asked for administrator password of + your local computer.

      Use this command if prefer graphical editor Gedit: - + If you prefer terminal editor vim simply run: - +       {{ getNextItem(hostsFileId) }} Make sure the line with the old hosts record is removed. Search and remove lines containing domain name:
      - +       {{ getNextItem(hostsFileId) }} Add (append) the new hosts record below to the text file:
      - + Make sure to avoid duplicate records.       {{ getNextItem(hostsFileId) }} Add (append) the hosts record below to the text file:
      - + Make sure to avoid duplicate records.       - - {{ getNextItem(hostsFileId) }} Save the changes and close your text editor. - + {{ getNextItem(hostsFileId) }} Save the changes and close your text editor. Next Next       - +

      # {{ workbenchId }}. Workbench - certificate

       - Follow installation of Workbench certificate to configure your access: @@ -899,28 +769,15 @@ const openSurvey = () => { - - Install Workbench certificate - + Install Workbench certificate - HUNT Workbench provides you with web-based access to modern data science tools such as Jupyter Notebooks, Python, RStudio, R and MATLAB. + HUNT Workbench provides you with web-based access to modern data science tools such as Jupyter Notebooks, + Python, RStudio, R and MATLAB. - + @@ -934,30 +791,12 @@ const openSurvey = () => { - - - + + + Make sure you have received your Workbench certificate ({{ labName }}-{{ username }}.p12). - - Assure working VPN connection. - + Assure working VPN connection. - - - - We recommend that you use Google Chrome browser for all HUNT Workbench applications to work correctly. + + + + We recommend that you use Google Chrome browser for all HUNT Workbench applications to work + correctly.
        +
      1. Open Google Chrome on your local computer.
        2. +
      2. Download our public CA certificate from https://pki.hdc.ntnu.no/hctsca1.crt
      3. - Open Google Chrome on your local computer. -
        4. -
      4. - Download our public CA certificate from https://pki.hdc.ntnu.no/hctsca1.crt -
        5. -
      5. - In Google Chrome, open the URL chrome://settings/certificates and navigate to section Authorities. -
        6. -
      6. - Click the Import button on the right side of the screen to import hctsca1.crt certificate file. + In Google Chrome, open the URL chrome://settings/certificates and navigate to section + Authorities.
        7. +
      7. Click the Import button on the right side of the screen to import hctsca1.crt certificate file.
      8. Select first option Trust this certificate for identifying websites.
        - import-ca-trust-websites + import-ca-trust-websites
      9. - Within chrome://settings/certificates navigate to section Your certificates - and click the Import button on the right side of the screen. -
        10. -
      10. - Browse and select your {{ labName}}-{{ username }}.p12 file that you downloaded to your local computer, - and enter the TLS passphrase that we sent you on Signal. + Within chrome://settings/certificates navigate to section + Your certificates and click the Import button on the right side of the screen.
      11. - Restart Google Chrome. + Browse and select your {{ labName }}-{{ username }}.p12 file that you downloaded to your local computer, and + enter the TLS passphrase that we sent you on Signal.
        12. +
      12. Restart Google Chrome.
       @@ -1022,71 +844,52 @@ const openSurvey = () => {       - - - + + + Make sure you are connected to the VPN before you access your HUNT Workbench. - - We recommend to use Google Chrome browser for all HUNT Workbench applications to work correctly. + + We recommend to use Google Chrome browser for all HUNT Workbench applications to work + correctly.
        -
      1. - Open your web browser. -
        2. +
      2. Open your web browser.
      3. Open the URL address below to access your lab in your web browser:
        - https://{{ fqdn }} + https://{{ fqdn }}

        You may get a User Identification Request for your new certificate.
        Verify that the certificates are issued by HUNT Cloud:
        - 
        +                            
        
+                              
                                       
-                            
        
+
        +

        Ensure that the Remember this decision box is checked, and click OK.
        - chrome_select_certificate_confirm + chrome_select_certificate_confirm
      4. Sign in with your HUNT Cloud username and lab passphrase.
        Lab passphrase is the same passphrase that you created yourself on your first SSH login.
        - - If you did not create a lab passphrase yet use a temporary SSH passphrase that you received - from us on Signal message to login and then follow passphrase change flow. + + If you did not create a lab passphrase yet use a temporary SSH passphrase that you received from us on Signal message to login and then follow + passphrase change flow.
        - workbench-login-form + workbench-login-form
      5. - With a little bit of luck you should now see your new HUNT Workbench. - Feel free to read our getting started guide. + With a little bit of luck you should now see your new HUNT Workbench. Feel free to read our + getting started guide.
        Click around and explore your new world!
        6. @@ -1095,95 +898,83 @@ const openSurvey = () => { JupyterLab - + Remember to bookmark your Lab address
        - https://{{fqdn}} + https://{{ fqdn }}         - - - - This section includes issues that you might encounter during your first setup. - See our HUNT Workbench FAQ and HUNT Workbench Troubleshooting if you do not find your answers below. - -
        This site can't be reached + + + This section includes issues that you might encounter during your first setup. See our + HUNT Workbench FAQ and + HUNT Workbench Troubleshooting if you do not find your answers below. + +
        + This site can't be reached
        - 1. If you are getting DNS_PROBE_FINISHED_NXDOMAIN error you need to repeat the {{ hostsFileId }}. Workbench - hosts file guide. -
        - 2. If you are getting ERR_CONNECTION_TIMED_OUT error you need to make sure that you are connected to VPN. If you are able to ssh into lab your VPN is fine, and you need to repeat the 6. Workbench - hosts file guide. + 1. If you are getting DNS_PROBE_FINISHED_NXDOMAIN error you need to repeat the + {{ hostsFileId }}. Workbench - hosts file guide. +
        + 2. If you are getting ERR_CONNECTION_TIMED_OUT error you need to make sure that you are connected to VPN. If you are able to ssh into lab + your VPN is fine, and you need to repeat the 6. Workbench - hosts file guide.
        -
        I don't remember my passphrase +
        + I don't remember my passphrase
        - Don't worry. Request a reset of SSH passphrase in our "do-science" Service desk. + Don't worry. Request a reset of SSH passphrase in our "do-science" Service + desk.
        -
        Nginx error - 403 Forbidden +
        + Nginx error - 403 Forbidden
        This error means that you are attempting to connect without client certificate. -

        +

        There are 3 different causes each requires a different approach
          -
        1. - If you have just installed a fresh client certificate, restart your computer to make sure certificates are applied. -
          2. +
        2. If you have just installed a fresh client certificate, restart your computer to make sure certificates are applied.

        3. - If you have not yet installed a fresh client certificate on this computer, review the section Install your certificates above. Start by click on blue button Start again. + If you have not yet installed a fresh client certificate on this computer, review the section Install your certificates above. + Start by click on blue button Start again.

        4. - If you have used Workbench in {{ labName }} lab before, this error means that your certificate expired and you can follow this link to request Workbench reissue. Once your request is processed we will send you a fresh certificate. + If you have used Workbench in {{ labName }} lab before, this error means that your certificate expired and you can follow this link to + request Workbench reissue. Once your request is processed we will + send you a fresh certificate.
        -
        Firefox - Did Not Connect +
        + Firefox - Did Not Connect
        - - We recommend to use Google Chrome browser for all HUNT Workbench applications to work correctly. + + We recommend to use Google Chrome browser for all HUNT Workbench applications to work + correctly. - Firefox may require that you manually import the HUNT Cloud Certificate Authority to consider it trusted. - - If you see Error code: SEC_ERROR_UNKNOWN_ISSUER when accessing Workbench follow these steps: + Firefox may require that you manually import the HUNT Cloud Certificate Authority to consider it trusted. If you see Error code: + SEC_ERROR_UNKNOWN_ISSUER when accessing Workbench follow these steps:
          -
        1. - Download our public CA certificate from https://pki.hdc.ntnu.no/hctsca1.crt -
          2. -
        2. - Open the following Firefox URL: about:preferences#privacy. -
          3. +
        3. Download our public CA certificate from https://pki.hdc.ntnu.no/hctsca1.crt
          4. +
        4. Open the following Firefox URL: about:preferences#privacy.
        5. Scroll down to section Certificates and click on View Certificates.
          @@ -1206,15 +997,15 @@ const openSurvey = () => {
        -
        Chrome on Ubuntu +
        + Chrome on Ubuntu
        1. - In Google Chrome, open the URL chrome://settings/certificates and navigate to section Authorities. -
          2. -
        2. - Search for HUNT Cloud certificates (org-HUNT Cloud Trust Services). + In Google Chrome, open the URL chrome://settings/certificates and navigate to section + Authorities.
          3. +
        3. Search for HUNT Cloud certificates (org-HUNT Cloud Trust Services).
        4. Edit the HCTS CA 1 certificate and select first option Trust this certificate for identifying websites.
          @@ -1225,11 +1016,13 @@ const openSurvey = () => {
        -
        502 Bad gateway +
        + 502 Bad gateway
        - A 502 Bad gateway error when accessing https://{{ fqdn }}/hub/home - is an indication that something is wrong with the configuration on the server side.
        - Contact us in your lab channel on Slack (#lab-{{ labName }}) or Service desk email further investigations. + A 502 Bad gateway error when accessing https://{{ fqdn }}/hub/home is an indication that + something is wrong with the configuration on the server side.
        + Contact us in your lab channel on Slack (#lab-{{ labName }}) or + Service desk email further investigations.
        @@ -1242,22 +1035,23 @@ const openSurvey = () => { - - After you have successfully completed all the steps, you can start using your Workbench environment by opening this URL address: https://{{ fqdn }} + After you have successfully completed all the steps, you can start using your Workbench environment by opening this URL address: + https://{{ fqdn }} -
        Workbench Control panel +
        + Workbench Control panel
        You can access Control panel on this URL address: https://{{ fqdn }}/hub/home @@ -1275,54 +1069,30 @@ const openSurvey = () => {

        # Where to go next

        - - mdi-check-circle + + mdi-check-circle

        You have configured your lab access

        -

        - Got 1 minute? Tell us how it went! -

        +

        Got 1 minute? Tell us how it went!

        - - mdi-emoticon-sad-outline - - - mdi-emoticon-neutral-outline - - - mdi-emoticon-happy-outline - + + mdi-emoticon-sad-outline + + + mdi-emoticon-neutral-outline + + + mdi-emoticon-happy-outline +

        - Feel free to continue reading our getting started guides and figure out which tools do you need for your work. -
        + Feel free to continue reading our getting started guides and figure out which + tools do you need for your work. +
        Otherwise, you're done!

        @@ -1338,20 +1108,15 @@ const openSurvey = () => { - - Optional guides - + Optional guides -

        # Copy SSH Public key

         - - 1. Open new Terminal window (CTRL + ALT + T). - + 1. Open new Terminal window (CTRL + ALT + T). 2. If you don't have xclip installed yet run installation. { 3. Run this command to copy SSH Public key created in Step 3 into clipboard. - - - - 3. Paste (CTRL+V) your SSH Public key where needed. + + 3. Paste (CTRL+V) your SSH Public key where needed.         @@ -1384,12 +1141,9 @@ const openSurvey = () => {

        # Troubleshooting

        - - WIP - + WIP -         @@ -1418,24 +1172,24 @@ pre code { background-color: unset; color: rgba(204, 204, 204, 1) !important; } -pre[class*=language-] { - margin: .85rem 0; +pre[class*="language-"] { + margin: 0.85rem 0; padding-bottom: 4px !important; padding-top: 4px !important; } -div[class*=language-] { +div[class*="language-"] { position: relative; background-color: #282c34; border-radius: 6px; overflow-x: unset; } -div[class*=language-]:before { +div[class*="language-"]:before { position: absolute; z-index: 3; - top: .8em; + top: 0.8em; right: 1em; - font-size: .75rem; - color: hsla(0, 0%, 100%, .4); + font-size: 0.75rem; + color: hsla(0, 0%, 100%, 0.4); } .v-overlay__content ul { @@ -1451,7 +1205,7 @@ div[class*=language-]:before { background-color: rgba(0, 0, 0, 0.05) !important; padding: 0.2em 0.4em; } -.v-overlay__content pre[class*=language-] { +.v-overlay__content pre[class*="language-"] { padding-bottom: 8px !important; padding-top: 8px !important; } diff --git a/docs/.vitepress/theme/components/lab-access/MacJourney.vue b/docs/.vitepress/theme/components/lab-access/MacJourney.vue index 9f478a26fc..801b29ac6a 100644 --- a/docs/.vitepress/theme/components/lab-access/MacJourney.vue +++ b/docs/.vitepress/theme/components/lab-access/MacJourney.vue @@ -163,6 +163,11 @@ const getNextItem = (groupId, reset = false) => { return `${groupId}.${itemId}.` } +function closeVpnDialog() { + vpnDialog.value = false + vpnStepper.value = 1 +} + // Lifecycle onMounted(() => { if (!filterGuidesByType.value && localStorage.hasOwnProperty("labAccessGuideFilter") && localStorage.labAccessGuideFilter) { @@ -267,8 +272,8 @@ const closeWorkbenchDialog = (workbenchStepperValue = null) => { - mdi-vpn  {{ filterGuidesByType && ['vpn_reset'].includes(filterGuidesByType) ? `OpenVPN Configuration` : `2. OpenVPN Configuration` }} - + mdi-vpn  {{ filterGuidesByType && ["vpn_reset"].includes(filterGuidesByType) ? `OpenVPN Configuration` : `2. OpenVPN Configuration` }} + diff --git a/docs/.vitepress/theme/components/lab-access/WindowsJourney.vue b/docs/.vitepress/theme/components/lab-access/WindowsJourney.vue index 08be2d8bc8..c62749e9fd 100644 --- a/docs/.vitepress/theme/components/lab-access/WindowsJourney.vue +++ b/docs/.vitepress/theme/components/lab-access/WindowsJourney.vue @@ -1,5 +1,5 @@ - - + + - +
          -
        1. - Right-click on the OpenVPN notification icon on the taskbar. -
          2. +
        2. Right-click on the OpenVPN notification icon on the taskbar.
        3. Select Connect.
          - 7-openvpn-click-connect + 7-openvpn-click-connect
        4. Enter your username: - +
        5. - Enter a rotating 6-digit verification code from Google Authenticator as your password.
          + Enter a rotating 6-digit verification code from Google Authenticator as your password.
          Do not save rotating password. Make sure that save password box is empty and then click OK.
          - 8-openvpn-totp-fill-guide + 8-openvpn-totp-fill-guide
        6. - When prompted for a Private Key Password, insert the VPN passphrase from Signal.
          + When prompted for a Private Key Password, insert the VPN passphrase from Signal.
          Make sure to save this long password and then click OK.
          - Your authentication will fail when you complete your passphrase below. - This is expected since your verification code timed out while you typed your passphrase.
          - 9-openvpn-passphrase-fill-guide + Your authentication will fail when you complete your passphrase below. This is expected since your + verification code timed out while you typed your passphrase.
          + 9-openvpn-passphrase-fill-guide
        7. - If the same window as in step 4 pops up try to connect again with a fresh verification code from Google Authenticator app. + If the same window as in step 4 pops up try to connect again with a fresh verification code from Google + Authenticator app.


        @@ -515,54 +450,31 @@ const openSurvey = () => { Back         - - + + - - + + OpenVPN-icon - Finish + Finish Start again Troubleshooting Back - - - - - + + + +

        # Authenticate VPN

        - If the Authenticate VPN prompt pops up again, then try to log in again with a new verification code. + If the Authenticate VPN prompt pops up again, then try to log in again with a new verification code.

        @@ -587,18 +499,18 @@ const openSurvey = () => {

        # Could not read Auth error

        - The error messages below indicates that TOTP (Google Auth) code is not accepted. - You should try to setup your TOTP one more time or request a TOTP reset in Service desk. - 
        +                          The error messages below indicates that TOTP (Google Auth) code is not accepted. You should try to setup your TOTP one more time or request a TOTP reset
+                          in Service desk.
+                          
        
+                            
                                     
-                          
        
+
        +

        # Could not read Private Key error

        -
        - The error messages below indicates that there is a typo in the Private Key Password (step 2.3.5) and you need to type it in again. -
        +
        The error messages below indicates that there is a typo in the Private Key Password (step 2.3.5) and you need to type it in again.
                                     ERROR: could not read Private Key username/password/ok/string from management interface
@@ -613,62 +525,64 @@ const openSurvey = () => {
 
                         
        
                         
        # Remove saved passphrase
        
+                        
        If you need to remove your VPN passphrase because of typo or SSH reissue.
        
                         
        
-                          If you need to remove your VPN passphrase because of typo or SSH reissue.
-                        
        
-                        
        
-                          Right click on the OpenVPN icon OpenVPN-icon in the task bar in the lower right corner of your screen and select Clear Saved Passwords.
+                          Right click on the OpenVPN icon
+                          OpenVPN-icon in the task bar in the
+                          lower right corner of your screen and select Clear Saved Passwords.
                         
        
 
                         
        
                         
        # Remove VPN config
        
+                        
        If you need to remove your VPN config because SSH reissue or reactivation.
        
                         
        
-                          If you need to remove your VPN config because SSH reissue or reactivation.
+                          Open your file explorer and manually remove the folder with the old OpenVPN configurations. It's usually located in this directory and you should remove
+                          the directory {{ username }} including the contents:
                         
        
-                        
        
-                          Open your file explorer and manually remove the folder with the old OpenVPN configurations.
-                          It's usually located in this directory and you should remove the directory {{ username }} including the contents:
-                        
        
-                        
+                        
 
                         
        
-                        
        # Route addition failed 
        
+                        
        # Route addition failed
        
                         
        
                           You should reinstall your OpenVPN with administrative rights if you already installed OpenVPN and are getting errors below:
-                          
        +                          
        
+                            
                                     
-                          
        
+                          
        
+                          
        
 
-                          
        +                          
        
+                            
                                     
-                          
        
+                          
        
+                          
        
 
-                          
        +                          
        
+                            
                                     
-                          
        
+                          
        
+                          
        
                         
        
 
                         
        
                         
        # TLS handshake failed
        
                         
        
                           If you see the error below the problem might be with your current network (e.g. institution is blocking VPN connections).
-                          
        +                          
        
+                            
                                     
-                          
        
+                          
        
+                          
        
 
                           
          
+                            
        • Make sure your IP address is in our Access list.
          • 
                             
        • 
-                              Make sure your IP address is in our Access list.
-                            
          • 
-                            
        • 
-                              Confirm that your local institution is blocking VPN connecting by connecting from different network (e.g. mobile internet or from home).
-                              For more details see our troubleshooting guide
-                              Cannot connect due to local firewalls.
+                              Confirm that your local institution is blocking VPN connecting by connecting from different network (e.g. mobile internet or from home). For more
+                              details see our troubleshooting guide
+                              Cannot connect due to local firewalls.
                             
          • 
                           
        
                         
        
@@ -678,31 +592,20 @@ const openSurvey = () => {
                         
        
                           If you want to check whether your VPN connection is blocked by the firewall, download and install [NMAP](https://nmap.org/download.html), and then run:
                         
        
-                        
+                        
                         
        
                           If traceroute ends with 129.241.176.121 no blocking was detected. If tracing seems stuck send us a screenshot in service desk.
                         
        
 
-                        
+                        
                           
-                          If nothing works, please head over to our main troubleshooting section for more information on how to troubleshoot connections.
+                          If nothing works, please head over to our main troubleshooting section for more
+                          information on how to troubleshoot connections.
                         
-
                       
                       Start again
                       Back
                     
-
                   
                 
               
@@ -726,13 +629,7 @@ const openSurvey = () => {
             
        # {{ passChangeId }}. SSH Passphrase change
        
           
           
-
-            
+            
               Ensure that you are logged into VPN.
             
 
@@ -743,9 +640,7 @@ const openSurvey = () => {
               poster="/img/video-covers/lab-access-macOS-ssh-passphrase-v1.jpg"
             />
 
-            
-              {{ getNextItem(passChangeId, true) }} Design .
-            
+             {{ getNextItem(passChangeId, true) }} Design . 
             
               {{ getNextItem(passChangeId) }} To start Command Prompt press WIN + R and type cmd.exe then hit Enter.
             
@@ -791,22 +686,13 @@ const openSurvey = () => {
        - + If you are getting an Authentication token manipulation error check strength requirements for passphrase in step {{ passChangeId }}.1. {{ getNextItem(passChangeId) }} Reconnect to entry using your new passphrase. - + Expected result: @@ -830,15 +716,19 @@ const openSurvey = () => { - 
        +              
        
+                
                       
-              
        
+
        +
        {{ getNextItem(passChangeId) }} Similar to above, you will be asked for a new password. Type your new passphrase two times. - 
        +              
        
+                
                       
-              
        
+
        +
        -

        # {{ sshConfId }}. SSH Config file

        +

        # {{ sshConfId }}. SSH Config file

         - { /> - {{ getNextItem(sshConfId, true) }} Open new Command Prompt window (WIN + R and type cmd.exe then hit Enter) and assure SSH Config file exists. No output is expected. + {{ getNextItem(sshConfId, true) }} Open new Command Prompt window (WIN + R and type cmd.exe then hit Enter) and assure SSH + Config file exists. No output is expected. { {{ getNextItem(sshConfId) }} Open SSH Config file. { {{ getNextItem(sshConfId) }} Remove old fingerprint. - + {{ getNextItem(sshConfId) }} Test by connecting straight into home machine. - - - - {{ getNextItem(sshConfId) }} Close Command Prompt to make sure you are disconnected from your lab. + + {{ getNextItem(sshConfId) }} Close Command Prompt to make sure you are disconnected from your lab. Next @@ -1036,15 +905,9 @@ const openSurvey = () => {

        # {{ hostsFileId }}. Workbench - hosts file

        - + - If you do not have Administrator permissions on your local workstation make sure to ask - IT department in your organization for assistance or permissions. + If you do not have Administrator permissions on your local workstation make sure to ask IT department in your organization for assistance or permissions. Let's set up your hosts file on your local computer.
        @@ -1057,77 +920,51 @@ const openSurvey = () => { poster="/img/video-covers/lab-access-macOS-workbench-hosts-v1.jpg" /> + {{ getNextItem(hostsFileId, true) }} Press the Windows key. + {{ getNextItem(hostsFileId) }} Type Notepad in the search field. - {{ getNextItem(hostsFileId, true) }} Press the Windows key. - - - {{ getNextItem(hostsFileId) }} Type Notepad in the search field. - - - {{ getNextItem(hostsFileId) }} In the search results, right-click Notepad and select Run as administrator. + {{ getNextItem(hostsFileId) }} In the search results, right-click Notepad and select Run as administrator.
        - notepad-administrator + notepad-administrator         - {{ getNextItem(hostsFileId) }} Confirm administrator permissions by clicking on Yes. + {{ getNextItem(hostsFileId) }} Confirm administrator permissions by clicking on Yes.
        - notepad-admin-confirm + notepad-admin-confirm         - {{ getNextItem(hostsFileId) }} In Notepad, start by selecting File > Open (CTRL + O). + {{ getNextItem(hostsFileId) }} In Notepad, start by selecting File > Open (CTRL + O).
        - notepad-open-file + notepad-open-file         {{ getNextItem(hostsFileId) }} Find the directory below:
        - - notepad-hosts-base-directory
        + + notepad-hosts-base-directory
         {{ getNextItem(hostsFileId) }} Show hidden files by changing type from Text documents (*.txt) to view All files.
        - notepad-all-files
        + notepad-all-files
         {{ getNextItem(hostsFileId) }} When a file named hosts appears in the list select it and click Open:
        - notepad-selected-hosts + notepad-selected-hosts
        {{ getNextItem(hostsFileId) }} Make sure the line with the old hosts record is removed. Search and remove lines containing domain name:
        - +         {{ getNextItem(hostsFileId) }} Add (append) the new hosts record below to the text file:
        - + Make sure to avoid duplicate records.         {{ getNextItem(hostsFileId) }} Add (append) the hosts record below to the text file:
        - + Make sure to avoid duplicate records.         @@ -1139,14 +976,14 @@ const openSurvey = () => {         - - +

        # {{ workbenchId }}. Workbench - certificate

         - { - - Install Workbench certificate - + Install Workbench certificate - HUNT Workbench provides you with web-based access to modern data science tools such as Jupyter Notebooks, Python, RStudio, R and MATLAB. + HUNT Workbench provides you with web-based access to modern data science tools such as Jupyter Notebooks, + Python, RStudio, R and MATLAB. - + @@ -1200,114 +1024,87 @@ const openSurvey = () => { - - + + - - + + Make sure you have received your Workbench certificate ({{ labName }}-{{ username }}.p12). - - Assure working VPN connection. - + Assure working VPN connection. Continue Skip to Troubleshooting - - + + - + Let's install the certificates that are required to allow traffic with HUNT Workbench that is located in your lab.

        1. - Open your .p12 certificate that you downloaded from FileSender. - Make sure the store location is set to Current User and click Next: + Open your .p12 certificate that you downloaded from FileSender. Make sure the store location is set to Current User and click + Next:
          - 1_cert_p12 + 1_cert_p12
        2. Click Next one more time.
          - 2_cert_p12 + 2_cert_p12
        3. - Fill in the TLS passphrase that you received on signal, and make sure the options are checked exactly as in the image. - Then click Next: + Fill in the TLS passphrase that you received on signal, and make sure the options are checked exactly as in the image. Then click + Next:
          - 3_cert_p12 + 3_cert_p12
        4. - Check the first option: Automatically select the certificate store based on the type of certificate. - Click Next: + Check the first option: Automatically select the certificate store based on the type of certificate. Click Next:
          - 4_cert_p12 + 4_cert_p12
        5. - You should now get a Completing the Certificate Import Wizard message. - Click Finish to complete the import: + You should now get a Completing the Certificate Import Wizard message. Click Finish to complete the import:
          - 5_cert_p12 + 5_cert_p12
        6. - The wizard will require a confirmation to install a certificate from us: HCTS CA 1 (HUNT Cloud Trust Services). - Our certificate is required to safely access your workbench environment. -

          - You will normally be asked to confirm our certificate only when you set up the HUNT Workbench for the first time. - Thus, if you see LAB instead of HCTS CA 1 skip to step 7. + The wizard will require a confirmation to install a certificate from us: HCTS CA 1 (HUNT Cloud Trust Services). Our certificate is required to safely + access your workbench environment.

          + You will normally be asked to confirm our certificate only when you set up the HUNT Workbench for the first time. Thus, if you see + LAB instead of HCTS CA 1 skip to step 7.

          Before clicking YES, confirm that you see our thumbprint (fingerprint):
          - 
          +                            
          
+                              
                                         
-                            
          
+
          +

          - 6_confirmCAcertificate + 6_confirmCAcertificate
        7. Similar to Step 6, you will also need to install a certificate for your lab (Lab CA),
          where your Lab name should appear. Click YES.
          - 7_confirmLabCAcertificate + 7_confirmLabCAcertificate
        8. Now quit your internet browser (we recommend Google Chrome browser)
          and restart it for the certificate to get recognized.
          - 8_import_success + 8_import_success
        @@ -1316,73 +1113,56 @@ const openSurvey = () => { Back         - - + + - - + + - - + +
          -
        1. - Open your web browser. -
          2. +
        2. Open your web browser.
        3. Open the URL address below to access your lab in your web browser:
          - https://{{ fqdn }} + https://{{ fqdn }}

          You may get a User Identification Request for your new certificate.
          Verify that the certificates are issued by HUNT Cloud:
          - 
          +                            
          
+                              
                                         
-                            
          
+
          +

          Ensure that the Remember this decision box is checked, and click OK.
          - chrome_select_certificate_confirm + chrome_select_certificate_confirm
        4. Sign in with your HUNT Cloud username and lab passphrase.
          Lab passphrase is the same passphrase that you created yourself on your first SSH login.
          - - If you did not create a lab passphrase yet use a temporary SSH passphrase that you received - from us on Signal message to login and then follow passphrase change flow. + + If you did not create a lab passphrase yet use a temporary SSH passphrase that you received from us on Signal message to login and then follow + passphrase change flow.
          - workbench-login-form + workbench-login-form
        5. - With a little bit of luck you should now see your new HUNT Workbench. - Feel free to read our getting started guide. + With a little bit of luck you should now see your new HUNT Workbench. Feel free to read our + getting started guide.
          Click around and explore your new world!
          6. @@ -1391,89 +1171,83 @@ const openSurvey = () => { JupyterLab - + - 
          +                          
          
+                            
                                       
-                          
          
+
          +
          - - Finish + Finish Start again Troubleshooting Back - - - + + + - - This section includes issues that you might encounter during your first setup. - See our HUNT Workbench FAQ and HUNT Workbench Troubleshooting if you do not find your answers below. + + This section includes issues that you might encounter during your first setup. See our + HUNT Workbench FAQ and + HUNT Workbench Troubleshooting if you do not find your answers below. -
          This site can't be reached +
          + This site can't be reached
          - 1. If you are getting DNS_PROBE_FINISHED_NXDOMAIN error you need to repeat the {{ hostsFileId }}. Workbench - hosts file guide. -
          - 2. If you are getting ERR_CONNECTION_TIMED_OUT error you need to make sure that you are connected to VPN. If you are able to ssh into lab your VPN is fine, and you need to repeat the 6. Workbench - hosts file guide. + 1. If you are getting DNS_PROBE_FINISHED_NXDOMAIN error you need to repeat the + {{ hostsFileId }}. Workbench - hosts file guide. +
          + 2. If you are getting ERR_CONNECTION_TIMED_OUT error you need to make sure that you are connected to VPN. If you are able to ssh into lab + your VPN is fine, and you need to repeat the 6. Workbench - hosts file guide.
          -
          I don't remember my passphrase +
          + I don't remember my passphrase
          - Don't worry. Request a reset of SSH passphrase in our "do-science" Service desk. + Don't worry. Request a reset of SSH passphrase in our "do-science" Service + desk.
          -
          Nginx error - 403 Forbidden +
          + Nginx error - 403 Forbidden
          This error means that you are attempting to connect without client certificate. -

          +

          There are 3 different causes each requires a different approach
            -
          1. - If you have just installed a fresh client certificate, restart your computer to make sure certificates are applied. -
            2. +
          2. If you have just installed a fresh client certificate, restart your computer to make sure certificates are applied.

          3. - If you have not yet installed a fresh client certificate on this computer, review the section Install your certificates above. Start by click on blue button Start again. + If you have not yet installed a fresh client certificate on this computer, review the section Install your certificates above. + Start by click on blue button Start again.

          4. - If you have used Workbench in {{ labName }} lab before, this error means that your certificate expired and you can follow this link to request Workbench reissue. Once your request is processed we will send you a fresh certificate. + If you have used Workbench in {{ labName }} lab before, this error means that your certificate expired and you can follow this link to + request Workbench reissue. Once your request is processed we will + send you a fresh certificate.
          -
          Firefox - Warning: Potential security risk ahead +
          + Firefox - Warning: Potential security risk ahead
          - Click on the Advanced button to find the Error code (Feilkode). -

          + Click on the Advanced button to find the Error code (Feilkode).

          Continue based on the error code:
            +
          • If you see error code: SEC_ERROR_UNKNOWN_ISSUER continue with the next step below.
          • - If you see error code: SEC_ERROR_UNKNOWN_ISSUER continue with the next step below. -
            • -
          • - If you see any other error code contacts us on Slack or send us general Service desk request. + If you see any other error code contacts us on Slack or send us + general Service desk request.
            Remember to include the error code and screenshot.
            • @@ -1481,32 +1255,25 @@ const openSurvey = () => {
          -
          Firefox - Did Not Connect (SEC_ERROR_UNKNOWN_ISSUER) +
          + Firefox - Did Not Connect (SEC_ERROR_UNKNOWN_ISSUER)
          - - + + - Firefox may require that you manually import the HUNT Cloud Certificate Authority to consider it trusted. - - If you see Error code: SEC_ERROR_UNKNOWN_ISSUER when accessing Workbench follow these steps: + Firefox may require that you manually import the HUNT Cloud Certificate Authority to consider it trusted. If you see Error code: + SEC_ERROR_UNKNOWN_ISSUER when accessing Workbench follow these steps:
            +
          1. Download our public CA certificate from https://pki.hdc.ntnu.no/hctsca1.crt
          2. - Download our public CA certificate from https://pki.hdc.ntnu.no/hctsca1.crt -
            3. -
          3. - Open the following Firefox URL: - + Open the following Firefox URL: + +
          4. Scroll down to section Certificates and click on View Certificates. @@ -1530,15 +1297,15 @@ const openSurvey = () => {
          -
          Chrome on Ubuntu +
          + Chrome on Ubuntu
          1. - In Google Chrome, open the URL chrome://settings/certificates and navigate to section Authorities. -
            2. -
          2. - Search for HUNT Cloud certificates (org-HUNT Cloud Trust Services). + In Google Chrome, open the URL chrome://settings/certificates and navigate to section + Authorities.
            3. +
          3. Search for HUNT Cloud certificates (org-HUNT Cloud Trust Services).
          4. Edit the HCTS CA 1 certificate and select first option Trust this certificate for identifying websites.
            @@ -1549,30 +1316,33 @@ const openSurvey = () => {
          -
          502 Bad gateway +
          + 502 Bad gateway
          - A 502 Bad gateway error when accessing https://{{ fqdn }}/hub/home - is an indication that something is wrong with the configuration on the server side.
          - Contact us in your lab channel on Slack (#lab-{{ labName }}) or Service desk email further investigations. + A 502 Bad gateway error when accessing https://{{ fqdn }}/hub/home is an indication that + something is wrong with the configuration on the server side.
          + Contact us in your lab channel on Slack (#lab-{{ labName }}) or + Service desk email further investigations.
          Start again Back - Close + Close - - After you have successfully completed all the steps, you can start using your Workbench environment by opening this URL address: https://{{ fqdn }} + After you have successfully completed all the steps, you can start using your Workbench environment by opening this URL address: + https://{{ fqdn }} -
          Workbench Control panel +
          + Workbench Control panel
          You can access Control panel on this URL address: https://{{ fqdn }}/hub/home @@ -1590,54 +1360,30 @@ const openSurvey = () => {

          # Where to go next

          - - mdi-check-circle + + mdi-check-circle

          You have configured your lab access

          -

          - Got 1 minute? Tell us how it went! -

          +

          Got 1 minute? Tell us how it went!

          - - mdi-emoticon-sad-outline - - - mdi-emoticon-neutral-outline - - - mdi-emoticon-happy-outline - + + mdi-emoticon-sad-outline + + + mdi-emoticon-neutral-outline + + + mdi-emoticon-happy-outline +

          - Feel free to continue reading our getting started guides and figure out which tools do you need for your work. -
          + Feel free to continue reading our getting started guides and figure out which + tools do you need for your work. +
          Otherwise, you're done!

          @@ -1650,16 +1396,12 @@ const openSurvey = () => {           - - - Optional guides - + Optional guides - @@ -1667,24 +1409,10 @@ const openSurvey = () => { - - Create terminal session - + Create terminal session - - Create remote desktop session - + Create remote desktop session @@ -1695,21 +1423,12 @@ const openSurvey = () => {

          # Copy SSH Public key

          - - 1. Open new Command Prompt window (WIN + R and type cmd.exe then hit Enter). - + 1. Open new Command Prompt window (WIN + R and type cmd.exe then hit Enter). 2. Run this command to copy SSH Public key into clipboard. - - - - 3. Paste (CTRL+V) your SSH Public key where needed. + + 3. Paste (CTRL+V) your SSH Public key where needed. @@ -1719,7 +1438,6 @@ const openSurvey = () => {

          # Troubleshooting

          - Removing saved OpenVPN passphrases and metadata { Confirm deletion with by typing Yes and then press Enter: - 
          +              
          
+                
                             
-              
          
+
          +
          Deleting OpenVPN config - + Confirm deletion with by pressing Y and then Enter: - 
          +              
          
+                
                             
-              
          
+
          +
          -           -           @@ -1797,23 +1512,23 @@ pre code { color: rgba(204, 204, 204, 1) !important; } -pre[class*=language-] { - margin: .85rem 0; +pre[class*="language-"] { + margin: 0.85rem 0; } -div[class*=language-] { +div[class*="language-"] { position: relative; background-color: #282c34; border-radius: 6px; } -div[class*=language-]:before { +div[class*="language-"]:before { position: absolute; z-index: 3; - top: .8em; + top: 0.8em; right: 1em; - font-size: .75rem; - color: hsla(0, 0%, 100%, .4); + font-size: 0.75rem; + color: hsla(0, 0%, 100%, 0.4); } .v-overlay__content ul { @@ -1829,7 +1544,7 @@ div[class*=language-]:before { background-color: rgba(0, 0, 0, 0.05) !important; padding: 0.2em 0.4em; } -.v-overlay__content pre[class*=language-] { +.v-overlay__content pre[class*="language-"] { padding-bottom: 8px !important; padding-top: 8px !important; } From 8f69ead1a581453bcfc0d01840b47711a4761635 Mon Sep 17 00:00:00 2001 From: kei5uke Date: Fri, 2 Oct 2026 13:55:52 +0200 Subject: [PATCH 2/2] fix: prettier --- .../components/lab-access/LinuxJourney.vue | 17 ++++++----------- .../theme/components/lab-access/MacJourney.vue | 5 ----- .../components/lab-access/WindowsJourney.vue | 15 +++++---------- 3 files changed, 11 insertions(+), 26 deletions(-) diff --git a/docs/.vitepress/theme/components/lab-access/LinuxJourney.vue b/docs/.vitepress/theme/components/lab-access/LinuxJourney.vue index 6996ffe919..5698d8388a 100644 --- a/docs/.vitepress/theme/components/lab-access/LinuxJourney.vue +++ b/docs/.vitepress/theme/components/lab-access/LinuxJourney.vue @@ -197,11 +197,6 @@ const getNextItem = (groupId, reset = false) => { return `${groupId}.${itemId}.` } -function closeVpnDialog() { - vpnDialog.value = false - vpnStepper.value = 1 -} - // Lifecycle onMounted(() => { if (!filterGuidesByType.value && localStorage.hasOwnProperty("labAccessGuideFilter") && localStorage.labAccessGuideFilter) { @@ -294,7 +289,7 @@ const openSurvey = () => { - + OpenVPN Configuration @@ -397,7 +392,7 @@ const openSurvey = () => {