Troubleshooting

If the web browser does not launch the expected application for a URL, check the following:

• Run scalus verify to check that the scalus configuration file syntax is correct.
• Check the log file (scalus.log) in the same location as the configuration file for any errors. A log entry should be generated when scalus is launched by the web browser.
• Run the command scalus info to check that the protocol is registered with the underlying OS as well as configured in the scalus configuration. This produces output similar to the following (if the protocol is not showing as Registered, then run scalus register -p protocol to register it with the OS):

     Protocol   Registered Description          Configured Command
     ------------------------------------------------------------------------------------------------
     rdp             yes        Windows RDP Client   (C:\windows\system32\mstsc.exe %GeneratedFile%)
     ssh             yes        Windows OpenSSH      (C:\windows\system32\cmd.exe /c C:\Windows\System32\OpenSSH\ssh.exe %User%@%Host%)
     telnet          no         Putty client         (C:\windows\system32\cmd.exe /c C:\Program Files\PuTTY\putty.exe -telnet %user%@%host%)   

• Run the command scalus launch -u url to manually launch the application configured for the protocol. If this does not run the expected application, run the command scalus launch -u url -p. This will not launch the application, but will report to stdout the list of parsed tokens, and the contents of the generated file.