GitHub user yunfan24 added a comment to the discussion: I have written one 
service which is importing a JSONfile for monitoring internally

Since the remote interface can be accessed normally, the problem might be in 
your local environment rather than in Hertzbeat. Please try accessing other 
interfaces locally to see if they work correctly. Generally, if you have 
started both the frontend and backend locally and the frontend application 
works fine, then accessing the backend interface should also be without issues, 
whether using port 4200 or 1157. Does the frontend page work properly? Can you 
provide corresponding screenshots?

To view port application information on Windows, use the following commands:

```bash
netstat -an | findstr :1157
```

This command lists all active connections and listening ports and filters the 
result to show only those related to port 1157.

You can also use the following command to see which processes are using which 
ports:

```bash
netstat -ano | findstr :1157
```

This command will show the PID (Process ID) of the process using port 1157. You 
can then use the `tasklist` command to identify the process:

```bash
tasklist | findstr <PID>
```

Replace `<PID>` with the actual Process ID you found in the previous step.

If you need to terminate a process that is using a specific port, you can use 
the following command:

```bash
taskkill /PID <PID> /F
```

Replace `<PID>` with the actual Process ID of the process you want to 
terminate. The `/F` flag forces the process to terminate.

These commands should help you diagnose and resolve any issues related to port 
usage on your local machine.

GitHub link: 
https://github.com/apache/hertzbeat/discussions/3092#discussioncomment-12324012

----
This is an automatically sent email for dev@hertzbeat.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@hertzbeat.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hertzbeat.apache.org
For additional commands, e-mail: dev-h...@hertzbeat.apache.org

Reply via email to