Question
I have changed my agent check-in port to port 80 while IIS is set to port 80 as well. Now the Kserver service will not start. What do I do?
Answer
Because of the port being set at 80 in the System > Server Management > Configure page as well as the IIS Default being set to use TCP Port 80, the Kaseya Service will not start. Here is what to do to resolve this:
Launch IIS Manager
Select Default Web Site > Properties
Change the TCP Port to 85 (or a random whatever/unused port)
Go to Services > Restart IIS Admin Service & World Wide Web Publishing Server
Open an IE Browser window
Visit http://localhost:85/ (or http://localhost:xx > where XX = the port you specified above) & login with a Kaseya Admin account
Visit System > Server Management > Configure
Start the Kserver Service > This will start with success
Change the Specify Port Agents field from 80 back to 5721 or an unused port > This will change with success
Exit the IE Browser Window
Launch IIS Manager
Select Default Web Site > Properties
Change the TCP Port back to 80
Go to Services > Restart IIS Admin Service & World Wide Web Publishing Server
Open IE
Launch http://localhost/
The Kaseya VSA properly loads w/ the KServer Service online.
More Information
Applies To
Kaseya
IIS
I have changed my agent check-in port to port 80 while IIS is set to port 80 as well. Now the Kserver service will not start. What do I do?
Have more questions?
Was this article helpful?
Provide feedback for the Documentation team!
Browse this section
- #vPatchConfiguration.LanCacheUNCPath# variable not storing value
- Agent Procedure Error "The File Exists"
- Agent procedure to Collect Windows Event Logs - Application and System Logs
- Agent Procedures - deleteDirectory with "recursively delete" option fails on agents with Italian Windows installation
- Agent Procedures - Execute User Command.
- Agent Procedures - WriteFile() fails to write files to C:\Windows\system32
- Agent Procedures appear to be scheduled by a user that is no longer with the company
- Agent Procedures are not approved even though they were created by a "Master" user.
- Agent Procedures show as Pending Approval
- Agent Procedures taking longer to execute
- See more