Skip to main content
Solved

assystServer and assystReport using the same management socket binding port: 9990

  • July 27, 2026
  • 2 replies
  • 17 views

BerenguerE
Sidekick (Employee)
Forum|alt.badge.img+5

Because of this configuration (that is not available for edit during installation process) and the fact that they’re installed on the same server, only one of the services starts… Can I change these settings, so they don’t conflict with each other?

 

 

Best answer by Alan Macfarlane

Hi

 

The settings are not exposed via the installer, so fine grained control still needs a manual update of the configuration file, or via the properties listed above as part of startup (i.e. passed to the shell script or via wrapper.conf is running on Windows as a service). However, the post offset property is exposed in the installer so you can bump all network ports up by that value. 

 

2 replies

Forum|alt.badge.img+7

Hi

 

The settings are not exposed via the installer, so fine grained control still needs a manual update of the configuration file, or via the properties listed above as part of startup (i.e. passed to the shell script or via wrapper.conf is running on Windows as a service). However, the post offset property is exposed in the installer so you can bump all network ports up by that value. 

 


BerenguerE
Sidekick (Employee)
Forum|alt.badge.img+5
  • Author
  • Sidekick (Employee)
  • July 28, 2026

Thank you very much ​@Alan Macfarlane ! I re-run the installer and set the offset port to 1 as you told me. The management socket binding ports changed and aren’t conflicting with assyst anymore. :)

:D

Best regards,

Elaine Berenguer