Closed githubaobab closed 11 months ago
Hi, After update a peertube 6 instance, i look in log, news errors :
[19/Dec/2023:02:00:01 +0100] "GET /.well-known/x-nodeinfo2 HTTP/1.1" 404 294 "-" "Friendica 'Giant Rhubarb' 2023.05-1518; https://friendicarg.nsupdate.info" "-" [19/Dec/2023:02:00:05 +0100] "GET /api/v1/directory?limit=1 HTTP/1.1" 400 5 "-" "Friendica 'Giant Rhubarb' 2023.05-1518; https://friendicarg.nsupdate.info" "-" [19/Dec/2023:02:00:06 +0100] "GET /poco HTTP/1.1" 406 5 "-" "Friendica 'Giant Rhubarb' 2023.05-1518; https://friendicarg.nsupdate.info" "-" [19/Dec/2023:02:00:08 +0100] "GET /api/v1/instance/activity HTTP/1.1" 400 5 "-" "Friendica 'Giant Rhubarb' 2023.05-1518; https://friendicarg.nsupdate.info" "-"
Is this normal ? with a fail2ban rules, many Ips are blacklisted ... this is a problem i think, maybe a Friendica problem ?
PeerTube instance:
Browser name, version and platforms on which you could reproduce the bug:
Link to browser console log if relevant:
Link to server log if relevant (journalctl or /var/www/peertube/storage/logs/):
journalctl
/var/www/peertube/storage/logs/
Hi,
You need to ask friendica developers. If they need something on peertube side, they can open an issue :)
Describe the current behavior
Hi, After update a peertube 6 instance, i look in log, news errors :
[19/Dec/2023:02:00:01 +0100] "GET /.well-known/x-nodeinfo2 HTTP/1.1" 404 294 "-" "Friendica 'Giant Rhubarb' 2023.05-1518; https://friendicarg.nsupdate.info" "-" [19/Dec/2023:02:00:05 +0100] "GET /api/v1/directory?limit=1 HTTP/1.1" 400 5 "-" "Friendica 'Giant Rhubarb' 2023.05-1518; https://friendicarg.nsupdate.info" "-" [19/Dec/2023:02:00:06 +0100] "GET /poco HTTP/1.1" 406 5 "-" "Friendica 'Giant Rhubarb' 2023.05-1518; https://friendicarg.nsupdate.info" "-" [19/Dec/2023:02:00:08 +0100] "GET /api/v1/instance/activity HTTP/1.1" 400 5 "-" "Friendica 'Giant Rhubarb' 2023.05-1518; https://friendicarg.nsupdate.info" "-"
Steps to reproduce
Describe the expected behavior
Is this normal ? with a fail2ban rules, many Ips are blacklisted ... this is a problem i think, maybe a Friendica problem ?
Additional information
PeerTube instance:
Browser name, version and platforms on which you could reproduce the bug:
Link to browser console log if relevant:
Link to server log if relevant (
journalctl
or/var/www/peertube/storage/logs/
):