![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 20/02/2021 21.36, Carlos E.R. wrote:
On 20/02/2021 21.14, Dave Howorth wrote:
On Sat, 20 Feb 2021 20:35:23 +0100 (CET) "Carlos E. R." <> wrote:
What it surprises me is that they hit such a high port, they have to be probing every port.
(The router is set to redirect incoming tcp on that high port to the inside server at the same high port)
My IP address changed on the 7 and 8 of February, the hits increase on the 10th. It is possible that the previous user of that IP had a known domain.
Unlikely, unless you chose a well-known high number. Switch to a random one.
Good idea, I will do that.
Well, I did that and now it doesn't work. I get timeouts on both Chrome and Firefox trying from the phone. I only changed the port number in router /etc/apache2/listen.conf /etc/apache2/vhosts.d/vhost.conf Ah! I forgot the firewall. :-D Nothing like writing an email to see the problem. Now it works. :-D Trying to write the URL in FF for Android when it fails is horribly difficult. When it fails, it tries google, and you no longer can edit it. Stupid. I had to go again to Chrome, share the (non working) URL to WhatsApp, then in Whatsapp tap on the URL and say open with FF. Interestingly, when I use Chrome in my phone to access the page, the access_log does include the full URL I typed: 176.*.*.200 - - [20/Feb/2021:22:51:56 +0100] "GET /favicon.ico HTTP/1.1" 404 1235 "http://host.domain:port/" "Mozilla/5.0 (Linux; Android 9; moto g(6) plus) AppleWeb Kit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.181 Mobile Safari/537.36" -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)