Re: Request to Establish a Debian Mirror Server for Bangladeshi Users

2023-11-08 Thread Jeffrey Walton
On Wed, Nov 8, 2023 at 4:51 AM Md Shehab wrote: > > I hope this email finds you well. I am writing to propose the establishment > of a Debian mirror server in Bangladesh > > I am confident that a Debian mirror server in Bangladesh would be a valuable > resource for the lo

Re: Request to Establish a Debian Mirror Server for Bangladeshi Users

2023-11-08 Thread Byung-Hee HWANG
On Wed, Nov 08, 2023 at 10:10:51AM +0600, Md Shehab wrote: > Dear Debian Community, > > I hope this email finds you well. I am writing to propose the establishment > of a Debian mirror server in Bangladesh > I am confident that a Debian mirror server in Bangladesh would be a >

Re: Request to Establish a Debian Mirror Server for Bangladeshi Users

2023-11-07 Thread Richard Hector
On 8/11/23 17:10, Md Shehab wrote: Dear Debian Community, I hope this email finds you well. I am writing to propose the establishment of a Debian mirror server in Bangladesh I am confident that a Debian mirror server in Bangladesh would be a valuable resource for the local tech community

Request to Establish a Debian Mirror Server for Bangladeshi Users

2023-11-07 Thread Md Shehab
Dear Debian Community, I hope this email finds you well. I am writing to propose the establishment of a Debian mirror server in Bangladesh I am confident that a Debian mirror server in Bangladesh would be a valuable resource for the local tech community I would like to request your support

Re: Debian, Git server, Nginx, Fcgiwrap, and git push can not create remote object directory

2023-09-10 Thread Geert Stappers
On Sat, Sep 09, 2023 at 04:31:38PM -0400, David Mehler wrote: > Hello, > > I'm trying to set up a git server on Debian 12, served by Nginx via > https. I used this as a debian-specific starter though I have done > this in the past using a FreeBSD and Apache type setup: > >

Re: Debian, Git server, Nginx, Fcgiwrap, and git push can not create remote object directory

2023-09-09 Thread David Mehler
er wrote: >> I'm trying to set up a git server on Debian 12, served by Nginx via >> https. I used this as a debian-specific starter though I have done >> this in the past using a FreeBSD and Apache type setup: >> >> https://esc.sh/blog/setting-up-a-git-http-server-

Debian, Git server, Nginx, Fcgiwrap, and git push can not create remote object directory

2023-09-09 Thread David Mehler
Hello, I'm trying to set up a git server on Debian 12, served by Nginx via https. I used this as a debian-specific starter though I have done this in the past using a FreeBSD and Apache type setup: https://esc.sh/blog/setting-up-a-git-http-server-with-nginx/ The client is a windows 10 client

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-06-01 Thread Tom Browder
On Wed, Jun 1, 2022 at 11:21 john doe wrote: > when does it actually start operating? Does it do so then, or does it take > > a reboot? > Apparently, if you 'enable' 'ufw', it will start and be enabled at boot. Good, thanks. According to (1), ufw should work with nftables, I did not follow

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-06-01 Thread john doe
On 6/1/2022 1:45 PM, Tom Browder wrote: On Mon, May 30, 2022 at 19:46 Edwin Zimmerman wrote: On 5/30/22 09:41, Greg Wooledge wrote: On Mon, May 30, 2022 at 07:13:54AM -0500, Tom Browder wrote: No worries. All those responses about the subject IP now are the norm for a bare-iron server

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-06-01 Thread Tom Browder
On Mon, May 30, 2022 at 19:46 Edwin Zimmerman wrote: > On 5/30/22 09:41, Greg Wooledge wrote: > > On Mon, May 30, 2022 at 07:13:54AM -0500, Tom Browder wrote: > >> No worries. All those responses about the subject IP now are the norm > for a > >> bare-iron server ready for use by a customer,

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-30 Thread Edwin Zimmerman
On 5/30/22 09:41, Greg Wooledge wrote: > On Mon, May 30, 2022 at 07:13:54AM -0500, Tom Browder wrote: >> No worries. All those responses about the subject IP now are the norm for a >> bare-iron server ready for use by a customer, yours truly. It is the same >> server I messed up the firewall with

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-30 Thread Timothy M Butterworth
On Mon, May 30, 2022 at 1:24 PM Tom Browder wrote: > On Mon, May 30, 2022 at 09:03 IL Ka wrote: > >> IMHO: It is better to have a firewall and block (policy -- drop) INPUT >> and FORWARD by default. >> And open only ports that must be opened. >> This will help if you install some software that

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-30 Thread Tom Browder
On Mon, May 30, 2022 at 09:03 IL Ka wrote: > IMHO: It is better to have a firewall and block (policy -- drop) INPUT and > FORWARD by default. > And open only ports that must be opened. > This will help if you install some software that listens for 0.0.0.0 by > accident > >From my limited

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-30 Thread Tom Browder
On Mon, May 30, 2022 at 08:42 Greg Wooledge wrote: .. > Unless this machine is more than just a web server...? It does serve other purposes.

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-30 Thread IL Ka
IMHO: It is better to have a firewall and block (policy -- drop) INPUT and FORWARD by default. And open only ports that must be opened. This will help if you install some software that listens for 0.0.0.0 by accident On Mon, May 30, 2022 at 4:42 PM Greg Wooledge wrote: > On Mon, May 30, 2022 at

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-30 Thread Greg Wooledge
On Mon, May 30, 2022 at 07:13:54AM -0500, Tom Browder wrote: > No worries. All those responses about the subject IP now are the norm for a > bare-iron server ready for use by a customer, yours truly. It is the same > server I messed up the firewall with and locked myself out of. The OS has > been

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-30 Thread Tom Browder
On Mon, May 30, 2022 at 02:13 john doe wrote: > On 5/30/2022 12:26 AM, Tom Browder wrote: > > On Sun, May 29, 2022 at 15:55 Greg Wooledge wrote: No worries. All those responses about the subject IP now are the norm for a bare-iron server ready for use by a customer, yours truly. It is the

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-30 Thread Curt
On 2022-05-29, Greg Wooledge wrote: > > Second, I cannot ping this IP address, nor can I telnet to port 80 of it. > (Nor port 22.) > That's strange; I can ping it (I'm not in Kansas anymore): curty@einstein:~$ ping 69.30.225.10 PING 69.30.225.10 (69.30.225.10) 56(84) bytes of data. 64 bytes

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-30 Thread john doe
On 5/30/2022 12:26 AM, Tom Browder wrote: On Sun, May 29, 2022 at 15:55 Greg Wooledge wrote: ... Thanks, Greg. It looks like my server was blocked from ports 80 and 443 upstream from it (as you and others suspected), so I asked my provider to reinstall the OS and ensure it has public access to

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread Charles Kroeger
> Maybe I should remove all firewall progs and start from zero. I would suggest you install Shorewall. it is not the pain in the arse that's been the theme of this thread so far.

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread Timothy M Butterworth
On Sun, May 29, 2022 at 8:13 PM Greg Wooledge wrote: > On Sun, May 29, 2022 at 11:50:44PM +, Lee wrote: > > On 5/29/22, Greg Wooledge wrote: > > > Second, I cannot ping this IP address, nor can I telnet to port 80 of > it. > > > > For whatever it's worth.. > > > > Pinging 69.30.225.10 with

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread IL Ka
> > > ssh gives me a login prompt > > Btw, I highly recommend: * Block SSH access from any IP except one you are going to use to manage this server * If you have dynamic IP, you can add all your ISP network, or, at least, your country: (list can be downloaded here

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread Greg Wooledge
On Sun, May 29, 2022 at 11:50:44PM +, Lee wrote: > On 5/29/22, Greg Wooledge wrote: > > Second, I cannot ping this IP address, nor can I telnet to port 80 of it. > > For whatever it's worth.. > > Pinging 69.30.225.10 with 32 bytes of data: > Reply from 69.30.225.10: bytes=32 time=43ms

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread Lee
On 5/29/22, Greg Wooledge wrote: > On Sun, May 29, 2022 at 03:39:05PM -0500, Tom Browder wrote: >> I have not intentionally hidden anything, Greg--I just never saw the need >> for >> mentioning it given the dialogue--x.y.z.w is just shorthand. If you >> must know the exact IP address, it is

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread Tom Browder
On Sun, May 29, 2022 at 15:55 Greg Wooledge wrote: ... Thanks, Greg. It looks like my server was blocked from ports 80 and 443 upstream from it (as you and others suspected), so I asked my provider to reinstall the OS and ensure it has public access to ports 80 and 443. Best regards, -Tom

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread Greg Wooledge
On Sun, May 29, 2022 at 03:39:05PM -0500, Tom Browder wrote: > I have not intentionally hidden anything, Greg--I just never saw the need for > mentioning it given the dialogue--x.y.z.w is just shorthand. If you > must know the exact IP address, it is 69.30.225.10. OK. Now we can actually start

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread Tom Browder
On Sun, May 29, 2022 at 2:21 PM Greg Wooledge wrote: > > > > > btw, are you able to ping server? > > > > > > Yes. > > > > It is always better to show the command and the output instead of saying > > yes/no! :) > > Except it should be abundantly clear by now that you're dealing with > someone who

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread Greg Wooledge
> > > btw, are you able to ping server? > > > > Yes. > > It is always better to show the command and the output instead of saying > yes/no! :) Except it should be abundantly clear by now that you're dealing with someone who believes that they must hide every single detail from the ones who

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread IL Ka
> > > I must say, I can not realy understand how you can ping and not > telnet/access your web server. > > Some router between OP and his server has something like -I FORWARD -j REJECT --reject-with icmp-host-unreachable

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread john doe
On 5/29/2022 7:20 PM, Tom Browder wrote: On Sun, May 29, 2022 at 11:39 IL Ka wrote: btw, are you able to ping server? Yes. It is always better to show the command and the output instead of saying yes/no! :) I must say, I can not realy understand how you can ping and not telnet/access

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread Tom Browder
On Sun, May 29, 2022 at 11:39 IL Ka wrote: > btw, are you able to ping server? > Yes.

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread tomas
On Sun, May 29, 2022 at 05:41:59AM -0500, Tom Browder wrote: > On Sat, May 28, 2022 at 20:06 IL Ka wrote: > ... > > 3. You should also check that Apache is running and listening to this port, > > use ``ss -lt``. > > For this command you _may_ use sudo to get process names (``sudo ss > > -ltp``).

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread IL Ka
btw, are you able to ping server? On Sun, May 29, 2022 at 7:26 PM Tom Browder wrote: > On Sun, May 29, 2022 at 10:33 AM IL Ka wrote: > > > > > >> When running those, I'm told neither the arptablrs nor the ebtables are > registered (not installed). Should I install them? > > > > No. > > > > So,

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread IL Ka
> > > > and ``iptables -S`` ? > > -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 61.177.173.50/32 -j REJECT --reject-with > icmp-port-unreachable > -A f2b-sshd -s 61.177.173.7/32 -j REJECT --reject-with >

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread Tom Browder
On Sun, May 29, 2022 at 10:33 AM IL Ka wrote: > > >> When running those, I'm told neither the arptablrs nor the ebtables are >> registered (not installed). Should I install them? > > No. > > So, you now have legacy (classic) iptables, right? Yes. > What is the output of ``iptables -L -v -n``

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread IL Ka
> When running those, I'm told neither the arptablrs nor the ebtables are > registered (not installed). Should I install them? > No. So, you now have legacy (classic) iptables, right? What is the output of ``iptables -L -v -n`` and ``iptables -S`` ?

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread Tom Browder
On Sun, May 29, 2022 at 09:51 IL Ka wrote: > >>> Do I have to switch all four *legacy *tables? >> > > yes > When running those, I'm told neither the arptablrs nor the ebtables are registered (not installed). Should I install them? >

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread IL Ka
> > >> Do I have to switch all four *legacy *tables? > yes

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread Tom Browder
On Sat, May 28, 2022 at 17:24 IL Ka wrote: > ... I am not familiar with nft, bit you can switch to iptables using >> ``update-alternatives`` >> > > # update-alternatives --set iptables /usr/sbin/iptables-legacy > # update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy > #

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread Erwan David
Le 29/05/2022 à 13:22, Tom Browder a écrit : On Sun, May 29, 2022 at 05:41 Tom Browder wrote: Does anyone have a good reason for me to NOT install and enable UFW? -Tom  good reason would be that thtere is obviously already something on your server magaing the firewalling. Having 2

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread IL Ka
> > > > Good to know. But does fail2ban require ipset? > No, but having several thousand rules is not convenient, so I prefer ipset > They never have before in over 15 years, and, before I got this server > started, its mate was serving fine. But if the ufw doesn't work, I'll ask > them. > I'd

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread Tom Browder
On Sun, May 29, 2022 at 07:06 IL Ka wrote: > Does anyone have a good reason for me to NOT install and enable UFW? >> > > ufw can't be used with ipset AFAIK, and I use ipset for many reasons > (fail2ban, block access outside of my country etc). > But If you only SSH your host from one static IP,

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread IL Ka
> > > > Does anyone have a good reason for me to NOT install and enable UFW? > > ufw can't be used with ipset AFAIK, and I use ipset for many reasons (fail2ban, block access outside of my country etc). But If you only SSH your host from one static IP, you probably do not need fail2ban at all.

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread IL Ka
> > $ telnet x.y.z.w 80 > Trying x.y.z.w... > telnet: Unable to connect to remote host: No route to host > But you can ssh to this host, right? Well, that means the firewall blocks your request and sends the ICMP message "no route to host". Switch to the legacy iptables using

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread Tom Browder
On Sun, May 29, 2022 at 05:41 Tom Browder wrote: Does anyone have a good reason for me to NOT install and enable UFW? -Tom

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-29 Thread Tom Browder
On Sat, May 28, 2022 at 20:06 IL Ka wrote: ... 3. You should also check that Apache is running and listening to this port, > use ``ss -lt``. > For this command you _may_ use sudo to get process names (``sudo ss > -ltp``). Read ``ss --help`` > > If you were able to connect on this host, then try

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-28 Thread Tom Browder
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

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-28 Thread IL Ka
> > > $ 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

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-28 Thread Tom Browder
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

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-28 Thread Tom Browder
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

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-28 Thread Timothy M Butterworth
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

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-28 Thread Greg Wooledge
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

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-28 Thread Tom Browder
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

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-28 Thread Tom Browder
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

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-28 Thread IL Ka
> > 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,

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-28 Thread Dan Ritter
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 >

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-28 Thread Tom Browder
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

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-28 Thread IL Ka
> > > > 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

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-28 Thread Tom Browder
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

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-28 Thread IL Ka
e > -A f2b-sshd -s 61.177.172.98/32 -j REJECT --reject-with > icmp-port-unreachable > -A f2b-sshd -s 122.160.233.137/32 -j REJECT --reject-with > icmp-port-unreachable > -A f2b-sshd -j RETURN > This is fail2ban chain to block bots, but I strongly suggest to use ipset and not to s

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-28 Thread Georgi Naplatanov
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.

Re: Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-28 Thread Dan Ritter
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

Firewall blocking my new Debian 11 server ports 80 and 443

2022-05-28 Thread Tom Browder
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:

Re: Debian on server

2020-01-21 Thread Linux-Fan
e a centos advantage. If I don't remember wrongly in the past HP had a list of supported server on debian but if today I will try to check OS/distro compatility I found only RH and Ubuntu. At this point, considering that ubuntu came from Debian, I suppose that also Debian can run on the server when ubuntu

Re: Debian on server

2020-01-21 Thread Alessandro Baggi
Il 21/01/20 18:30, Linux-Fan ha scritto: Andy Smith writes: Hi, On Tue, Jan 21, 2020 at 03:41:13PM +0100, Alessandro Baggi wrote: > So, I know this is a debian list and could be obtain biased opinion but > what are better point to use debian on a server instead of CentOS? Really I

Re: Debian on server

2020-01-21 Thread Linux-Fan
Andy Smith writes: Hi, On Tue, Jan 21, 2020 at 03:41:13PM +0100, Alessandro Baggi wrote: > So, I know this is a debian list and could be obtain biased opinion but > what are better point to use debian on a server instead of CentOS? Really I think you are best off using whichever one yo

Re: Debian on server

2020-01-21 Thread Joe
know this is a debian list and could be obtain biased opinion > but what are better point to use debian on a server instead of CentOS? > A difference which may be significant to you is that Debian stable can always be upgraded in place to the next major version, while even now I think the ad

Re: Debian on server

2020-01-21 Thread mick crane
biased opinion but what are better point to use debian on a server instead of CentOS? Thanks in advance. running a server facing the internet would give me the jitters but if it's just for you as Andy says whatever you are comfortable with. As far as I know a server is a distribution with only

Re: Debian on server

2020-01-21 Thread Andy Smith
Hi, On Tue, Jan 21, 2020 at 03:41:13PM +0100, Alessandro Baggi wrote: > So, I know this is a debian list and could be obtain biased opinion but what > are better point to use debian on a server instead of CentOS? Really I think you are best off using whichever one you have the most expe

Off-topic email usage note (Was: Debian on server)

2020-01-21 Thread John Hasler
When quoting someone don't include the "-- " signature marker. Some people have their email software configured to not show signatures. Including that will make your response invisible to them. It's also conventional to precede quoted lines with ">". -- John Hasler jhas...@newsguy.com

Re: Debian on server

2020-01-21 Thread Alessandro Baggi
le distro for server. Many said CentOS and other Debian but really I have not enough experiences to choose one. So, I know this is a debian list and could be obtain biased opinion but what are better point to use debian on a server instead of CentOS? Thanks in advance. Main d

Re: Debian on server

2020-01-21 Thread Default User
enough experiences > to choose one. > > So, I know this is a debian list and could be obtain biased opinion but > what are better point to use debian on a server instead of CentOS? > > Thanks in advance. > > Main difference between Debian and CentOS distros is package manageme

Re: Debian on server

2020-01-21 Thread Alexander V. Makartsev
debian list and could be obtain biased opinion > but what are better point to use debian on a server instead of CentOS? > > Thanks in advance. > Main difference between Debian and CentOS distros is package management system. I prefer APT and DEB packages because it is more intuitive,

Debian on server

2020-01-21 Thread Alessandro Baggi
to use debian on a server instead of CentOS? Thanks in advance.

Re: Can't login to Debian buster server after upgrade from stretch

2019-12-02 Thread Klaus Singvogel
David wrote: > I offer this as "level-1 support" :) general information, I don't know > exactly what the problem is, but if you cut and paste here the output of > 'ssh -v ...' then someone here can give you better advice based on that. That's excatly the same issue I run in with this report too.

Re: Can't login to Debian buster server after upgrade from stretch

2019-12-02 Thread David
On Tue, 3 Dec 2019 at 16:02, Joe Aquilina wrote: > "David" Tue, 3 Dec 2019 15:13:42 +1100 > On Tue, 3 Dec 2019 at 14:36, Joe Aquilina wrote: > > Upgraded a Debian stretch machine to buster yesterday morning. All seemed > > to go fine but I can no longer SSH in to that server. I get the

Re: Can't login to Debian buster server after upgrade from stretch

2019-12-02 Thread Joe Aquilina
  - Original Message -From: "David" To:"debian-user" Cc: Sent:Tue, 3 Dec 2019 15:13:42 +1100 Subject:Re: Can't login to Debian buster server after upgrade from stretch On Tue, 3 Dec 2019 at 14:36, Joe Aquilina wrote: > Upgraded a Debian stretch machine to b

Re: Can't login to Debian buster server after upgrade from stretch

2019-12-02 Thread David
On Tue, 3 Dec 2019 at 14:36, Joe Aquilina wrote: > Upgraded a Debian stretch machine to buster yesterday morning. All seemed to > go fine but I can no longer SSH in to that server. I get the following when I > try to login: > packet_write_wait: Connection to port 22: Broken pipe > I found

Can't login to Debian buster server after upgrade from stretch

2019-12-02 Thread Joe Aquilina
Upgraded a Debian stretch machine to buster yesterday morning. All seemed to go fine but I can no longer SSH in to that server. I get the following when I try to login: packet_write_wait: Connection to port 22: Broken pipe I found some pages on the net that suggest

Re: bad printing results (was: Why choose Debian on server)

2019-04-03 Thread Cindy Sue Causey
On 1/4/19, Felix Miata wrote: > deloptes composed on 2019-01-04 22:32 (UTC+0100): > >> Gene Heskett wrote: > >>> My copy of FF only prints 1 page, which is the top 3" of the site's >>> front page, never getting down to any of the text past the headline. > >>> And it works on other sites. > >>

Re: Have you used Duplicati 2.0.4.5 to backup Debian 9.8.0 Server?

2019-03-15 Thread Gene Heskett
On Friday 15 March 2019 06:37:12 Curt wrote: > On 2019-03-15, Dan Ritter wrote: > > Borg integrates nicely as a method for ninjabackup. I recommend > > them. > > curty@einstein:~$ apt-cache search ninja > backupninja - lightweight, extensible meta-backup system > > > curty@einstein:~$ apt-cache

Re: Have you used Duplicati 2.0.4.5 to backup Debian 9.8.0 Server?

2019-03-15 Thread Curt
On 2019-03-15, Dan Ritter wrote: > > Borg integrates nicely as a method for ninjabackup. I recommend > them. curty@einstein:~$ apt-cache search ninja backupninja - lightweight, extensible meta-backup system curty@einstein:~$ apt-cache show backupninja Backupninja is a silent flower blossom

Re: Have you used Duplicati 2.0.4.5 to backup Debian 9.8.0 Server?

2019-03-15 Thread Dan Ritter
deloptes wrote: > Turritopsis Dohrnii Teo En Ming wrote: > > > Good morning from Singapore, > > > > Have you used Duplicati 2.0.4.5 to backup Debian 9.8.0 Server? > > > > Is it good? > > > > Thank you for your review. > > I was loo

Re: Have you used Duplicati 2.0.4.5 to backup Debian 9.8.0 Server?

2019-03-15 Thread deloptes
Turritopsis Dohrnii Teo En Ming wrote: > Good morning from Singapore, > > Have you used Duplicati 2.0.4.5 to backup Debian 9.8.0 Server? > > Is it good? > > Thank you for your review. I was looking recently for a backup solution and did review few of them. I choose borg.

Have you used Duplicati 2.0.4.5 to backup Debian 9.8.0 Server?

2019-03-15 Thread Turritopsis Dohrnii Teo En Ming
Good morning from Singapore, Have you used Duplicati 2.0.4.5 to backup Debian 9.8.0 Server? Is it good? Thank you for your review. ===BEGIN EMAIL SIGNATURE=== The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy

Re: Why choose Debian on server

2019-01-15 Thread David Wright
On Wed 09 Jan 2019 at 20:43:19 (+), Brian wrote: > On Wed 09 Jan 2019 at 12:47:42 -0600, David Wright wrote: > > On Mon 07 Jan 2019 at 23:51:36 (+), Brian wrote: > > > On Mon 07 Jan 2019 at 14:37:30 -0600, David Wright wrote: > > > > On Mon 07 Jan 2019 at 18:21:07 (+), Brian wrote: > >

Re: Why choose Debian on server

2019-01-11 Thread francis picabia
as an Apache server - the way Debian does it with dozens of little files to enable is harder for someone with Redhat background to master. The bonus with CentOS/Redhat is long support lifecycle. You can install it and keep it running for up to 10 years, with updates. Debian does not do that, however

Re: Why choose Debian on server

2019-01-10 Thread Gene Heskett
On Sunday 06 January 2019 12:56:14 Brian wrote: > On Sun 06 Jan 2019 at 12:15:09 -0500, Gene Heskett wrote: > > [...] > > > > > > screenshot filename.png --fullpage > > > > Humm: > > gene@coyote:~/linuxcnc/nc_files$ sudo apt-get install screenshot > > Reading package lists... Done > > Building

Re: Why choose Debian on server

2019-01-10 Thread Curt
On 2019-01-06, Brian wrote: > > Thank you for your persistence. I was beginning to think your Firefox > was not from Debian. It appears the feature you describe has disappeared > from it in more recent versions: > > https://www.ghacks.net/2018/05/21/firefox-62-developer-toolbar-removal/ > It

Re: Why choose Debian on server

2019-01-09 Thread Brian
On Wed 09 Jan 2019 at 12:47:42 -0600, David Wright wrote: > On Mon 07 Jan 2019 at 23:51:36 (+), Brian wrote: > > On Mon 07 Jan 2019 at 14:37:30 -0600, David Wright wrote: > > > On Mon 07 Jan 2019 at 18:21:07 (+), Brian wrote: > > > > On Sun 06 Jan 2019 at 18:13:58 -0600, David Wright

Re: Why choose Debian on server

2019-01-09 Thread David Wright
On Mon 07 Jan 2019 at 23:51:36 (+), Brian wrote: > On Mon 07 Jan 2019 at 14:37:30 -0600, David Wright wrote: > > On Mon 07 Jan 2019 at 18:21:07 (+), Brian wrote: > > > On Sun 06 Jan 2019 at 18:13:58 -0600, David Wright wrote: > > > > > > [...] > > > > > > > BTW if this Screenshot method

Re: Why choose Debian on server

2019-01-08 Thread Curt
On 2019-01-05, Gene Heskett wrote: > > I think the question about is it on purpose on the part of stackexchange In researching this bug, I recently discovered bugzilla.mozilla.org itself triggers the bug. Just drumming up business, as it were, I guess.

Re: Why choose Debian on server

2019-01-07 Thread Brian
On Mon 07 Jan 2019 at 14:37:30 -0600, David Wright wrote: > On Mon 07 Jan 2019 at 18:21:07 (+), Brian wrote: > > On Sun 06 Jan 2019 at 18:13:58 -0600, David Wright wrote: > > > > [...] > > > > > BTW if this Screenshot method is meant to yield a "printable" > > > document, I haven't yet

Re: Why choose Debian on server

2019-01-07 Thread David Wright
On Mon 07 Jan 2019 at 18:21:07 (+), Brian wrote: > On Sun 06 Jan 2019 at 18:13:58 -0600, David Wright wrote: > > [...] > > > BTW if this Screenshot method is meant to yield a "printable" > > document, I haven't yet figured out how to print it sensibly. > > $ lp -d PDF very-long-image.png

Re: Why choose Debian on server

2019-01-07 Thread Brian
On Sun 06 Jan 2019 at 18:13:58 -0600, David Wright wrote: [...] > BTW if this Screenshot method is meant to yield a "printable" > document, I haven't yet figured out how to print it sensibly. > $ lp -d PDF very-long-image.png gives me the image on one page, > and looks, as it happens, like the

Re: Why choose Debian on server

2019-01-07 Thread deloptes
Curt wrote: > Then you, if I'm remembering correctly, joined in to profess your own > distrust or dislike of stackexchange and your refusal to use Chromium to > obviate a very long-standing FF bug that you appear to claim or strongly > suggest only impacts the stackexchange web site. > I bag a

Re: Why choose Debian on server

2019-01-07 Thread Curt
On 2019-01-06, deloptes wrote: > Curt wrote: > >> I have no different opinion (I don't think). I know nothing about >> stackexchange. I am indifferent to stackexchange. However, if you want >> to print that full thread on stackexchange, like *Gene wanted to print >> that full thread*, and your

Re: Why choose Debian on server

2019-01-06 Thread David Wright
On Sun 06 Jan 2019 at 12:15:09 (-0500), Gene Heskett wrote: > On Sunday 06 January 2019 11:28:55 David Wright wrote: > > On Sun 06 Jan 2019 at 10:37:48 (-0500), Gene Heskett wrote: > > > On Sunday 06 January 2019 10:17:16 Brian wrote: > > > > On Sun 06 Jan 2019 at 14:42:08 +0100, deloptes wrote: >

Re: long page screenshots (was: Why choose Debian on server)

2019-01-06 Thread Felix Miata
Curt composed on 2019-01-06 18:53 (UTC): > Brian wrote: >> What is your version of FF? (Help/About Firefox). > I found it. Tools --> Web Developer --> Toggle Tools (checked) > In the console > :screenshot foo --fullpage > https://developer.mozilla.org/en-US/docs/Tools/Web_Console/Helpers >

Re: Why choose Debian on server

2019-01-06 Thread David Wright
On Sun 06 Jan 2019 at 16:53:03 (+), Brian wrote: > On Sun 06 Jan 2019 at 10:28:55 -0600, David Wright wrote: > > On Sun 06 Jan 2019 at 10:37:48 (-0500), Gene Heskett wrote: > > > On Sunday 06 January 2019 10:17:16 Brian wrote: > > > > Maybe he would like to use SHIFT+F2 with Firefox (I have

  1   2   3   4   5   6   >