Resolving Access Issues to CF Service
If you're encountering difficulties accessing the CF service, please follow the steps below to diagnose and potentially resolve the issue:
Preliminary Check:
Browser Compatibility: The service was successfully tested on multiple computers, including ones running Microsoft Edge. Ensure you're using a compatible browser.
Initial Troubleshooting Steps:
Restart the CF Service:
Open Command Prompt.
Navigate to the installation folder using
cd
command.Execute
nucleusd --stop
to stop the service. Wait for the confirmation that the service has stopped.Start the service again by typing
nucleusd --start
. Check if the issue persists.
Service Startup Type:
If restarting the service works, consider setting its startup type to Automatic (Delayed Start) in the service properties. This allows for other necessary Windows core services to initiate before the CF service starts, ensuring smoother operation.
-
Additional Steps if the Issue Continues:
URL Format: Attempt accessing the service via
http://localhost:9090/
. Ensure thathttp://
is included in the URL, not just127.0.0.1
.DNS Settings: Verify the DNS settings to ensure they are not mistakenly searching for the domain
127.0.0.1
.Port Scan:
Conduct a port scan to check if port 9090 is responsive.
Open Windows PowerShell with admin rights (Press Windows + X > select "Windows PowerShell (Admin)").
Use the
Test-NetConnection
cmdlet to test the connection. Example:powershell
Test-NetConnection -ComputerName localhost -Port 9090
Replace
localhost
with127.0.0.1
if necessary, and9090
with the port you're checking.Note: Ensure you have the necessary permissions to perform port scans to avoid unauthorized activity.
Environmental Check:
Installation Oversight: Determine if the PC setup was done independently or if the customer's IT department was involved. This can help identify if the issue is local to your setup or broader.
Conflict Check:
Consider temporarily stopping the CF service to investigate if other services are running on the same port. While web services typically run on ports 80 or 8080, conflicts can arise with other applications.
Final Notes:
Always proceed with caution when making system changes and ensure you have the appropriate permissions, especially when performing actions like port scans that might affect network security or compliance.
Test-NetConnection -ComputerName localhost -Port 9090