Re: on to letsencrypt

On 20/04/2021 13:32, Jack Craig wrote: Well as of tomorrow morning I will be down to two problems the first problem is my primary DNS server is not listening / connecting g/conneenin on external IP As port 53 is still closed you may want to post your named.conf -- Remind me to ignore comment

Re: on to letsencrypt

Well as of tomorrow morning I will be down to two problems the first problem is my primary DNS server is not listening / connecting g/conneenin on external IP the second problem is the secondary IP as identified by AT&T to be my secondary refusing to reply is refusing to provide answers below

Re: on to letsencrypt

On 20/04/2021 10:02, Jack Craig wrote: Sorry it's been a long day on the phone with AT&T only to find out I got nowhere yeah I'm tired I made a few mistakes today my apologies OK. Well let us know when you think you have thinks working.  I see you've not yet configured it at 12:50GMT+8. [root

Re: on to letsencrypt

Sorry it's been a long day on the phone with AT&T only to find out I got nowhere yeah I'm tired I made a few mistakes today my apologies thanks for your corrections now that's what's really important is what's the right thing to do so again thanks for your help On Mon, Apr 19, 2021 at 6:57 PM Ed

Re: on to letsencrypt

On 20/04/2021 09:27, Jack Craig wrote: on the other hand, ... ;O nmap -sS 108.220.213.121 Starting Nmap 7.80 ( https://nmap.org ) at 2021-04-19 18:26 PDT Nmap scan report for ws (108.220.213.121) Host is up (0.0014s latency). Not shown: 994 closed ports PORT      STATE SERVIC

Re: on to letsencrypt

On 20/04/2021 09:25, Jack Craig wrote: On Mon, Apr 19, 2021 at 5:27 PM Ed Greshko mailto:ed.gres...@greshko.com>> wrote: On 20/04/2021 07:31, Jack Craig wrote: > > > On Mon, Apr 19, 2021 at 3:11 PM Ed Greshko mailto:ed.gres...@greshko.com>

Re: on to letsencrypt

on the other hand, ... ;O nmap -sS 108.220.213.121 Starting Nmap 7.80 ( https://nmap.org ) at 2021-04-19 18:26 PDT Nmap scan report for ws (108.220.213.121) Host is up (0.0014s latency). Not shown: 994 closed ports PORT STATE SERVICE 80/tcpopen http 443/tcp open https 631/tcp open

Re: on to letsencrypt

On Mon, Apr 19, 2021 at 5:27 PM Ed Greshko wrote: > > On 20/04/2021 07:31, Jack Craig wrote: > > > > > > On Mon, Apr 19, 2021 at 3:11 PM Ed Greshko > wrote: > > > > On 19/04/2021 03:18, Jack Craig wrote: > > > > > > On Fri, Apr 16, 2021, at 10:56 AM

Re: on to letsencrypt

On 20/04/2021 07:31, Jack Craig wrote: On Mon, Apr 19, 2021 at 3:11 PM Ed Greshko mailto:ed.gres...@greshko.com>> wrote: On 19/04/2021 03:18, Jack Craig wrote: > >     On Fri, Apr 16, 2021, at 10:56 AM, Ed Greshko wrote: >     > On 16/04/2021 17:19, Ed Greshko wrote: >   

Re: on to letsencrypt

On Mon, Apr 19, 2021 at 3:11 PM Ed Greshko wrote: > On 19/04/2021 03:18, Jack Craig wrote: > > > > On Fri, Apr 16, 2021, at 10:56 AM, Ed Greshko wrote: > > > On 16/04/2021 17:19, Ed Greshko wrote: > > > > On 16/04/2021 10:35, Jack Craig wrote: > > > >> First I get my static IP fro

Re: on to letsencrypt

On 19/04/2021 03:18, Jack Craig wrote: On Fri, Apr 16, 2021, at 10:56 AM, Ed Greshko wrote: > On 16/04/2021 17:19, Ed Greshko wrote: > > On 16/04/2021 10:35, Jack Craig wrote: > >> First I get my static IP from AT&T actually a block of eight addresses of which only the first do

wayward wayland.

While trying to diagnose problems as a part of another thread in this list, I discovered that wayland is not functional on my workstation. I'm currently logged in to gnome using the top "GNOME" entry in the menu of desktops that is displayed in the upper right corner of the monitor during login