Re: chromium: ERR_CONNECTION_REFUSED

2021-02-12 Thread Rainer Dorsch
Am Freitag, 12. Februar 2021, 21:39:10 CET schrieb Jeremy Ardley:
> On 13/2/21 4:15 am, Rainer Dorsch wrote:
> > Hi,
> > 
> > I suddenly cannot access my local managed switch anymore from chromium:
> > 
> > Chromium tries to swtich to the HTTPS protocol but the switch only
> > supports
> > HTTP protocol
> > 
> > The error message I get is
> > 
> > ERR_CONNECTION_REFUSED
> > 
> > Chromium 83 still worked.
> > 
> > Is there a way avoid this automatic switch for a site?
> > 
> > Thanks
> > Rainer
> 
> Chrome behaviour has become more intolerant of https and http over the
> past year or so - to the point it is unusable of there is any
> certificate problems.
> Firefox is going the same way.

Firefox still lets to log into the switch (Netgear JGS524PE). But here it 
seems that since ESR78 there is a (probably a javascript) incompatibility with 
the switch and it does not change settings.

> For problematic sites I use GNU Web instead. It will be perfectly
> adequate to access your switch web page.

I found the konqueror works as well. Usually it is the other way round.

Thanks
Rainer
-- 
Rainer Dorsch
http://bokomoko.de/




Re: chromium: ERR_CONNECTION_REFUSED

2021-02-12 Thread Rainer Dorsch
Am Freitag, 12. Februar 2021, 21:29:21 CET schrieb Roberto C. Sánchez:
> On Fri, Feb 12, 2021 at 09:15:35PM +0100, Rainer Dorsch wrote:
> > Hi,
> > 
> > I suddenly cannot access my local managed switch anymore from chromium:
> > 
> > Chromium tries to swtich to the HTTPS protocol but the switch only
> > supports
> > HTTP protocol
> > 
> > The error message I get is
> > 
> > ERR_CONNECTION_REFUSED
> > 
> > Chromium 83 still worked.
> > 
> > Is there a way avoid this automatic switch for a site?
> 
> Did you use the device IP or hostname without the protocol prefix?  From
> what I have observed, if I put just the IP or hostname, e.g.,
> "192.168.1.1" without specifying the protocol it defaults to HTTPS.
> However, if I include the protocol, e.g., "http://192.168.1.1; then the
> browser should respect that and try to default to HTTPS.
> 

Thanks for your quick reply. The first page load, but when I submit the 
password, I get the ERR_CONNECTION_REFUSED and I see that it tries to access 
https.

Rainer

-- 
Rainer Dorsch
http://bokomoko.de/




chromium: ERR_CONNECTION_REFUSED

2021-02-12 Thread Rainer Dorsch
Hi,

I suddenly cannot access my local managed switch anymore from chromium:

Chromium tries to swtich to the HTTPS protocol but the switch only supports 
HTTP protocol

The error message I get is

ERR_CONNECTION_REFUSED

Chromium 83 still worked.

Is there a way avoid this automatic switch for a site? 

Thanks
Rainer

-- 
Rainer Dorsch
http://bokomoko.de/




Re: chromium: ERR_CONNECTION_REFUSED

2021-02-12 Thread Jeremy Ardley


On 13/2/21 4:44 am, Georgi Naplatanov wrote:

On 2/12/21 10:39 PM, Jeremy Ardley wrote:

For problematic sites I use GNU Web instead. It will be perfectly
adequate to access your switch web page.



What is GNU Web, does Debian have package for it?

Kind regards
Georgi



My error Gnome Web. not GNU Web. I thnk it comes from epiphany package

https://gitlab.gnome.org/GNOME/epiphany

sudo apt install epiphany-browser epiphany-web-data


It shows as 'Web' in the gnome Internet sub-menu

--
Jeremy



OpenPGP_signature
Description: OpenPGP digital signature


Re: chromium: ERR_CONNECTION_REFUSED

2021-02-12 Thread Kenneth Parker
On Fri, Feb 12, 2021, 4:01 PM Kenneth Parker  wrote:

>
>
> On Fri, Feb 12, 2021, 3:51 PM Georgi Naplatanov  wrote:
>
>> On 2/12/21 10:39 PM, Jeremy Ardley wrote:
>> >
>> > For problematic sites I use GNU Web instead. It will be perfectly
>> > adequate to access your switch web page.
>> >
>>
>> What is GNU Web, does Debian have package for it?
>>
>
> I know of GNU IceCat.  Is that what is being referred to here?
>

I answered my own question:  There's also a "Gnome Web", originally called
Epiphany.

And, referring to my prior response, IceCat may not be, directly packaged
under Debian.  (At least I don't see it).

Kenneth Parker
>
>>


Re: chromium: ERR_CONNECTION_REFUSED

2021-02-12 Thread Kenneth Parker
On Fri, Feb 12, 2021, 3:51 PM Georgi Naplatanov  wrote:

> On 2/12/21 10:39 PM, Jeremy Ardley wrote:
> >
> > For problematic sites I use GNU Web instead. It will be perfectly
> > adequate to access your switch web page.
> >
>
> What is GNU Web, does Debian have package for it?
>

I know of GNU IceCat.  Is that what is being referred to here?

>
> Kind regards
> Georgi
>

Kenneth Parker

>


Re: chromium: ERR_CONNECTION_REFUSED

2021-02-12 Thread Georgi Naplatanov
On 2/12/21 10:39 PM, Jeremy Ardley wrote:
> 
> For problematic sites I use GNU Web instead. It will be perfectly
> adequate to access your switch web page.
> 


What is GNU Web, does Debian have package for it?

Kind regards
Georgi



Re: chromium: ERR_CONNECTION_REFUSED

2021-02-12 Thread Jeremy Ardley


On 13/2/21 4:15 am, Rainer Dorsch wrote:

Hi,

I suddenly cannot access my local managed switch anymore from chromium:

Chromium tries to swtich to the HTTPS protocol but the switch only supports
HTTP protocol

The error message I get is

ERR_CONNECTION_REFUSED

Chromium 83 still worked.

Is there a way avoid this automatic switch for a site?

Thanks
Rainer



Chrome behaviour has become more intolerant of https and http over the 
past year or so - to the point it is unusable of there is any 
certificate problems.

Firefox is going the same way.

For problematic sites I use GNU Web instead. It will be perfectly 
adequate to access your switch web page.


--
Jeremy



OpenPGP_signature
Description: OpenPGP digital signature


Re: chromium: ERR_CONNECTION_REFUSED

2021-02-12 Thread Roberto C . Sánchez
On Fri, Feb 12, 2021 at 09:15:35PM +0100, Rainer Dorsch wrote:
> Hi,
> 
> I suddenly cannot access my local managed switch anymore from chromium:
> 
> Chromium tries to swtich to the HTTPS protocol but the switch only supports 
> HTTP protocol
> 
> The error message I get is
> 
> ERR_CONNECTION_REFUSED
> 
> Chromium 83 still worked.
> 
> Is there a way avoid this automatic switch for a site? 
> 
Did you use the device IP or hostname without the protocol prefix?  From
what I have observed, if I put just the IP or hostname, e.g.,
"192.168.1.1" without specifying the protocol it defaults to HTTPS.
However, if I include the protocol, e.g., "http://192.168.1.1; then the
browser should respect that and try to default to HTTPS.

Regards,

-Roberto

-- 
Roberto C. Sánchez