On Sat, May 28, 2022 at 20:06 IL Ka wrote:
>
>> $ sudo su
>> # telnet 80
>> Trying 0.0.0.80...
>>
>
> 1. You are using telnet wrong: it should be "telnet [host] [port]". Please
> read "man telnet".
> 2. You do not need sudo to use telnet, do not do that
> 3. You should also check that
>
>
> $ sudo su
> # telnet 80
> Trying 0.0.0.80...
>
1. You are using telnet wrong: it should be "telnet [host] [port]". Please
read "man telnet".
2. You do not need sudo to use telnet, do not do that
3. You should also check that Apache is running and listening to this port,
use ``ss
On Sat, May 28, 2022 at 19:10 Timothy M Butterworth <
timothy.m.butterwo...@gmail.com> wrote:
…
On the local host try running `telnet 127.0.0.1 80`
>
I was able to connect, thanks, Timothy!
Now what? I would really like to use ufw.
-Tom
On Sat, May 28, 2022 at 19:01 Greg Wooledge wrote:
> On Sat, May 28, 2022 at 05:51:38PM -0500, Tom Browder wrote:
> …
>
> ... wow. Just wow. How can such a short excerpt contain so many failures?
Greg, calm down. I get it, but I haven’t unlearned years of muscle
memory—sorry.
And the telnet
On Sat, May 28, 2022 at 7:52 PM Tom Browder wrote:
>
>
> On Sat, May 28, 2022 at 17:51 Tom Browder wrote:
>
>> On Sat, May 28, 2022 at 17:30 IL Ka wrote:
>>
>>> I am running an Apache server and using Qualys Lab’s server checker. It
shows no access to the server.
Have you tried t
On Sat, May 28, 2022 at 05:51:38PM -0500, Tom Browder wrote:
> $ sudo su
> # telnet 80
> Trying 0.0.0.80...
... wow. Just wow. How can such a short excerpt contain so many failures?
1) "sudo su" is stupid. You don't need TWO setuid programs to get a root
shell. Either use "sudo
On Sat, May 28, 2022 at 17:51 Tom Browder wrote:
> On Sat, May 28, 2022 at 17:30 IL Ka wrote:
>
>> I am running an Apache server and using Qualys Lab’s server checker. It
>>> shows no access to the server.
>>>
>>> Have you tried to telnet to port 80 from home? Do you see apache
>> listening this
On Sat, May 28, 2022 at 17:30 IL Ka wrote:
> I am running an Apache server and using Qualys Lab’s server checker. It
>> shows no access to the server.
>>
>> Have you tried to telnet to port 80 from home? Do you see apache
> listening this port using ``ss``?
>
On the new host I did:
$ sudo s
>
> I am running an Apache server and using Qualys Lab’s server checker. It
> shows no access to the server.
>
> Have you tried to telnet to port 80 from home? Do you see apache
listening this port using ``ss``?
>
> Whatever attempt I make to change the ports disappears when I reboot.
>
> Sure,
Tom Browder wrote:
> On Sat, May 28, 2022 at 14:11 Tom Browder wrote:
>
> > As the bare-iron server came from my long-time cloud provider (since
> > Debian 6), incoming ports 80 and 443 are blocked.
>
>
> A little more digging shows the new server is using fail2ban and nft
> tables, so I
> nee
On Sat, May 28, 2022 at 17:08 Dan Ritter wrote:
…
Therefore, something outside of your machine is blocking the
> ports, or you are misreading or misusing the tools that are
> telling you the ports are blocked.
Tell us how you are checking the ports
I am running an Apache server and using Qual
>
>
>
> A little more digging shows the new server is using fail2ban and nft
> tables, so I
> need help on how to properly allow https and http inbound.
>
>
I am not familiar with nft, bit you can switch to iptables using
``update-alternatives``
# update-alternatives --set iptables /usr/sbin/iptab
On 2022-05-28 at 17:11, Greg Wooledge wrote:
> On Sat, May 28, 2022 at 04:02:39PM -0400, The Wanderer wrote:
>
>> On 2022-05-28 at 15:40, Jim Popovitch wrote:
>> > I have a file of regex patterns and I use grep like so:
>> >
>> >~$ grep -f patterns.txt /var/log/syslog
>> >
>> > What I'd lik
On Sat, May 28, 2022 at 04:02:39PM -0400, The Wanderer wrote:
> On 2022-05-28 at 15:40, Jim Popovitch wrote:
> > I have a file of regex patterns and I use grep like so:
> >
> >~$ grep -f patterns.txt /var/log/syslog
> >
> > What I'd like to get is a listing of all lines, specifically the lin
On Sat, May 28, 2022 at 14:11 Tom Browder wrote:
> As the bare-iron server came from my long-time cloud provider (since
> Debian 6), incoming ports 80 and 443 are blocked.
A little more digging shows the new server is using fail2ban and nft
tables, so I
need help on how to properly allow https
On 2022-05-28 at 15:40, Jim Popovitch wrote:
> Not exactly Debian specific, but hoping that someone here can help.
>
> I have a file of regex patterns and I use grep like so:
>
>~$ grep -f patterns.txt /var/log/syslog
>
> What I'd like to get is a listing of all lines, specifically the lin
>
>
>
> -P INPUT ACCEPT
> -P FORWARD ACCEPT
> -P OUTPUT ACCEPT
> -N f2b-sshd
> -A INPUT -p tcp -m multiport --dports 22 -j f2b-sshd
> -A f2b-sshd -s 62.204.41.56/32 -j REJECT --reject-with
> icmp-port-unreachable
> -A f2b-sshd -s 61.177.173.48/32 -j REJECT --reject-with
> icmp-port-unreachable
> -A
Not exactly Debian specific, but hoping that someone here can help.
I have a file of regex patterns and I use grep like so:
~$ grep -f patterns.txt /var/log/syslog
What I'd like to get is a listing of all lines, specifically the line
numbers of the regexps in patterns.txt, that match entries
On 5/28/22 22:11, Tom Browder wrote:
> As the bare-iron server came from my long-time cloud provider (since
> Debian 6), incoming ports 80 and 443 are blocked.
>
> I ran my usual iptables command for new servers from them, but this
> time the default settings were different so it didn't work.
Try
Tom Browder wrote:
> As the bare-iron server came from my long-time cloud provider (since
> Debian 6), incoming ports 80 and 443 are blocked.
>
> I ran my usual iptables command for new servers from them, but this
> time the default settings were different so it didn't work.
>
> Output from "sud
As the bare-iron server came from my long-time cloud provider (since
Debian 6), incoming ports 80 and 443 are blocked.
I ran my usual iptables command for new servers from them, but this
time the default settings were different so it didn't work.
Output from "sudo iptables -S" before my attempt:
On Sat, May 28, 2022, 11:08 AM Cindy Sue Causey
wrote:
> On 5/28/22, Thomas Schmitt wrote:
> > Hi,
> >
> > Brian wrote:
> >> > Careful! If you go on like this you will end up installing bullseye
> :).
> >
> > Keith Bainbridge wrote:
> >> Bookworm?
> >> SID?
> >
> > In any case: Not Testing !
> >
On 5/28/22, Thomas Schmitt wrote:
> Hi,
>
> Brian wrote:
>> > Careful! If you go on like this you will end up installing bullseye :).
>
> Keith Bainbridge wrote:
>> Bookworm?
>> SID?
>
> In any case: Not Testing !
>
> Currently a zillion of packages get marked for autoremovial from Testing
> becau
Hi,
Brian wrote:
> > Careful! If you go on like this you will end up installing bullseye :).
Keith Bainbridge wrote:
> Bookworm?
> SID?
In any case: Not Testing !
Currently a zillion of packages get marked for autoremovial from Testing
because of
https://bugs.debian.org/cgi-bin/bugreport.cgi?
On 24/5/22 23:23, Brian wrote:
Hi,
After my surrender to Jessie I've thought of moving on with Stretch.
Careful! If you go on like this you will end up installing bullseye :).
Bookworm?
SID?
--
All the best
Keith Bainbridge
keithrbaugro...@gmail.com
25 matches
Mail list logo
