HTTP is no longer supported (or: connection failures starting 2021-11-22)

[qtvr01]

maintainer edit

Firefox changed their policies to require HTTPS. See #208 (comment) for more detail.

original issue follows

As it was updated on the 22nd, http disappeared and only https were left. Can you let me do http again?

[patchper]

Same here. Failed to connect to NAS.

[8bitgentleman]

Same here, can't connect to a non https address

[CyberMachin]

Same after PC reinstallation and configuring this Google Chrome extension.
Is this problem due to the DSM upgrade or the extension ?

[8bitgentleman]

Personally I didn't have any upgrade between extension versions

[CyberMachin]

I try to do the same as my ancient configuration... I tried IP, NetBios, myDS nothing works. ;-(

[PatrickCras]

Same problem here, no connection after update.

[sungjucho]

Same here. My connection to NAS only supports http so that it fails. Is this change related to some new policies for Chrome?

[seansfkelley]

Unfortunately, no.

I had to make this change to comply with Firefox's incoming add-on policies that are effective December 1st:

Add-ons must use encryption when transporting data remotely.

As a workaround you can manually downgrade to 0.11.1, which presumably Firefox will continue to allow due to it not being the current version of the extension.

I'm sorry about the way this was rolled out -- I don't have any good messaging channels to warn about incoming changes, and I should have included a more-specific error message in the case where the extension knew you were using HTTP. That ship has sailed, so instead I've added an entry to the FAQ and I'll be pinning and updating this issue for anyone else who finds their way here.

If you choose to switch to using HTTPS, you'll probably have to configure your browser to accept the certificate.

[xBot55]

Same problem after uninstallation / installation for chrome and switch to HTTPS.

[seansfkelley]

@xBot55 that may be a proper bug. Can you take a look at https://github.com/seansfkelley/nas-download-manager/blob/master/FAQ.md and if that doesn't help, file a new issue with more detail?

[Thiefsie]

Is there an easy way to set up my synology to login with https?

Pity as I'm not running firefox but having the same problem

[razfag]

Is there an easy way to set up my synology to login with https?

Pity as I'm not running firefox but having the same problem

I did run into the same problem but figured it out, the http download station api runs on port 5000 the https on 5001

• Goto https://<nas_ip_address>:5001 in your browser
• In the invalid certificate warning advanced -> confirm security exception
• change the port in the addon settings to 5001

[Thiefsie]

Is there an easy way to set up my synology to login with https?
Pity as I'm not running firefox but having the same problem

I did run into the same problem but figured it out, the http download station api runs on port 5000 the https on 5001

• Goto https://<nas_ip_address>:5001 in your browser
• In the invalid certificate warning advanced -> confirm security exception
• change the port in the addon settings to 5001

Thanks you very much. That worked a treat.

[qtvr01]

Is there an easy way to set up my synology to login with https?
Pity as I'm not running firefox but having the same problem

I did run into the same problem but figured it out, the http download station api runs on port 5000 the https on 5001

• Goto https://<nas_ip_address>:5001 in your browser
• In the invalid certificate warning advanced -> confirm security exception
• change the port in the addon settings to 5001

In the invalid certificate warning advanced -> confirm security exception

Can you tell me in detail where to set this up?

[razfag]

@qtvr01 Not sure what to tell you. It's called differently on chome & firefox but behaves the same. It's just the warning you get when you try to open a website that has a invalid or self-signed certificate (like syno uses)

Eventually you have to login on the nas with the same credentials on the nas afterwards inside that browser tab over https once.

[borse2008]

This guide helped me configure DSM 7 from http setup to https. Now working for me.

https://mariushosting.com/synology-how-to-enable-https-on-dsm-7/

[Shawzborne]

So I managed to get DSM 6.2.4 switched over to HTTPS on my DS1817+ however I would appreciate if someone can post an easier guide than this one [](https://kb.synology.com/en-my/DSMUC/tutorial/How_to_enable_HTTPS_and_create_a_certificate_signing_request_on_your_Synology_Unified_Controller on how to setup a certificate for HTTPS/SSL) so that we don't get the certificate warnings every time DSM is opened in chrome. Please and thank-you

[papinist]

Is there an easy way to set up my synology to login with https?
Pity as I'm not running firefox but having the same problem

I did run into the same problem but figured it out, the http download station api runs on port 5000 the https on 5001

• Goto https://<nas_ip_address>:5001 in your browser
• In the invalid certificate warning advanced -> confirm security exception
• change the port in the addon settings to 5001

This should be pinned on top.. thank you!

[Otto42]

Still doesn't work. How does one manually downgrade? Where is the old 0.11.1 version available from?

[wickedgalen]

Hi,

I got the same issue.

Experience so far:

Windows 10 : the solution was installing, self-signed certificates, generated by my NAS. This worked more or less smooth, although the issue will come back as the certificate will only last 1 year. (.cer files)

Linux : although I installed the same certificates (conversion from .pem to .crt , update & reboot ) the Browser does not accept it I cannot setup the Add-On. (The process here is quite painful compared to Windows)

Additionally for both systems or any :

Could the add-on at least save the settings although not working ? avoiding to retype them every time ?

Also I specifically configured my NAS to send all HTTP traffic to HTTPS in case of missing the "S" resolving in a Forbidden Error, although this could be a NAS issue.

Also I noticed Chrome seems to have less difficulties accepting the certificates than Firefox.

The only thing working is directly accessing the NAS sadly defying the purpose of the addon.

Simply accepting the security risk in the browser is rarely working.

I hope this can be fixed.

If someone has another working solution I'm eager to try.