The NoSpamProxy Command Center cannot connect to the Intranet Role

If the NoSpamProxy Command Centre is unable to connect to the Intranet Role, there are two possible causes.

Incorrect PowerShell remoting configuration

  • Verify that all NoSpamProxy services are started.
  • Use the PowerShell to check whether the certificate for the NoSpamProxy Web App is assigned to the correct port. To do this, enter the following command:
Copy 
netsh http show sslcert

If this is not the case, enter the following command:

Copy 
netsh http add sslcert ipport=0.0.0.0:6061 "appid={6D46C289-5847-4017-BCEF-72920BD7E01F}" certhash=<<IhrZertifikats-HashWert>> certstorename=my
  • If a certificate is already bound but this no longer works, you can renew the entry with the following command:
Copy 
netsh http update sslcert ipport=0.0.0.0:6061 "appid={6D46C289-5847-4017-BCEF-72920BD7E01F}" certhash=<<IhrZertifikats-HashWert>> certstorename=my

Incorrect JWT configuration

  1. Stop the Intranet Role.

  2. Go to C:\ProgramData\Net at Work Mail Gateway\Configuration.

  3. Move the following files to a folder outside the Configuration folder.

    • jwt-config.json

    • jwt-key-private.pem

    • jwt-key-public.json

  4. Restart the Intranet Role. The JWT files should be regenerated automatically.

  5. Check whether authentication via NoSpamProxy is working. If this is the case, the files that were previously moved can be deleted.