Miranda Byrd
12/10/2023, 1:48 AMjournalctl
) that a number of http requests had been received in the few days that it was up.
Here's a snippet of logs:
Dec 05 08:54:22 localhost.localdomain prefect[3885809]: Check out the dashboard at <http://0.0.0.0:4200>
Dec 06 00:15:25 localhost.localdomain prefect[3885809]: Invalid HTTP request received.
Dec 06 01:32:59 localhost.localdomain prefect[3885809]: Invalid HTTP request received.
[...]
Dec 09 17:28:28 localhost.localdomain prefect[3885809]: Invalid HTTP request received.
Dec 09 17:32:56 localhost.localdomain systemd[1]: Stopping prefect-server.service - Prefect Server...
Unfortunately there's no other information available about the nature of the requests, so it's difficult to tell if they were port-scanning, or just problems with an open tab that refreshed from time to time. Is there any way to view more detailed logs about http requests received and responses set under default configuration, or would I have had to set something differently in my config (and can't get this info now, post-hoc)
Cheers,
MiraMiranda Byrd
12/10/2023, 1:49 AMTim Galvin
12/10/2023, 3:33 AMInvalid HTTP request received
errors as well, and I am running a self-hosted prefect server that is not accessible outside my company's private network. I would also be curious to find out whether they are related to prefect flow runs, or just any old network sniffer poking around.Tim Galvin
12/14/2023, 3:25 AMInvalid HTTP request received
messages were. In my case I was trying to hit the https URL, which I have not configured on my self-hosted server. They were automatically redirected to http and this error was emittedTim Galvin
12/14/2023, 3:25 AM