Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] binhex - DelugeVPN

binhex
in Docker Containers

Featured Replies

27 minutes ago, tmor2 said:

Again, code that you introduced to DelugeVPN is a security risk, but alas, users will find out themselves in an ugly way.

Troll.

  • Quote
    • Like 2
    • Replies 10.8k
    • Views 2.4m
    • Created
    • Last Reply

    Top Posters In This Topic

    Popular Days

    Most Popular Posts

    • Ryanoc3ros
      Ryanoc3ros

      Found the solution on reddit.   Due to the recent change in the authentication process, using your email and password for the manual connection method will no longer work. You will need to u

    • shaunsund
      shaunsund

      How to set up ProtonVPN in Deluge   I thought I'd share how I configured binhex-delugevpn to use ProtonVPN for those fellow paying ProtonVPN users. I don't know if this will work for the fre

    • Dad_Rage
      Dad_Rage

      I wanted to summarize how I got Mullvad working with DelugeVPN as I had to piece together several "solutions" from different comments in this thread and there was some incorrect info; likely old.

    Posted Images

    2 hours ago, Knh68 said:

    but i got my sonarr and radarr dockers webui working by adding their ports not just to the bottom of the edit screen and mapping the ports, but i added them to the vpn input and vpn output ports as well in deluge

    Just incidentally did i do right by doing this guys....? Also i use the openvpn rather than wireguard on pia. 

    Also can you load more than one   . Ovpn server to openvpn folder will it jump on to another automatically if it goes down or can you only have one server loaded at a time? 

    Hope i make sense lol 

  • Quote
    2 minutes ago, Knh68 said:

    Just incidentally did i do right by doing this guys....? Also i use the openvpn rather than wireguard on pia. 

    Also can you load more than one   . Ovpn server to openvpn folder will it jump on to another automatically if it goes down or can you only have one server loaded at a time? 

    Hope i make sense lol 

    https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

     

    Scroll down to Q20.

     

    I have noticed though that sometimes my PIA servers will have issues that result in very slow transfers but never actually go down so it’s still sometimes necessary to switch endpoints manually by editing the ovpn file.

  • Quote
    7 hours ago, wgstarks said:

    https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

     

    Scroll down to Q20.

     

    I have noticed though that sometimes my PIA servers will have issues that result in very slow transfers but never actually go down so it’s still sometimes necessary to switch endpoints manually by editing the ovpn file.

    So reading that article tgen, i don't need to add another .Ovpn server file to the ovpn folder...... Just alter the config file for different servers? 

     

  • Quote
    • Author
    So reading that article tgen, i don't need to add another .Ovpn server file to the ovpn folder...... Just alter the config file for different servers? 
     
    Correct

    Sent from my CLT-L09 using Tapatalk

  • Quote

    I tried searching the thread and have read the github FAQ. I don't think I've come across this question.

     

    I've had wireguard successfully running for a long time. Today, it looks like mullvad changed one of their endpoints I was using and/or they are having issues with the endpoint. Absolutely nothing to do with the container/functionality. Obviously I couldn't access the gui, searched the logs and it was issues with mullvad connecting.

     

    So I grabbed a new set off endpoints from them, deleted the old wg.conf file, uploaded a new endpoint, chowned it properly and blam it worked again like magic as I expected it would.

     

    My question is - when we get these VPN endpoints from the providers, they are usually bundled up into a dozen or so endpoints in a zip file per whatever location you select. I obviously used one of those. Is there some best practice to be able to change the endpoint? I gather I could just open wg.conf file and edit that but I was wondering what happens for example if I just throw all the endpoint conf files in the wireguard directory? Will it just use the first one? Or will it bug out? Can I just leave the others there for quick reference?

     

    This is obviously an extremely small annoyance and has nothing to do with the container itself but how wireguard operates. Since I have files all over the place I'm just wondering if I could drop them in the wireguard folder, so I could just ssh in and have the files there for copy and pasting. I'm assuming with how wireguard operates I couldn't create a script that if the first one failed it would use the next etc.

     

    As always thank you so much binhex for maintaining these containers they are awesome.

     

     

     

     

    Edited by Zervun

  • Quote
    19 minutes ago, Zervun said:

    Can I just leave the others there for quick reference?

    I use OpenVPN rather than wireguard but typically I store the zip file in the same folder with my ovpn file. The docker ignores it but it’s handy if I need it. I haven’t tried this with wireguard but I think it will likely work just as well.

     

    Another option might be to put all the endpoint files in the folder and name them so that the one you want to use will be the first found by the app. I haven’t tried this at all though so can’t say how it would turn out. You’ld have to test. Not sure how the docker searches for the file or if it’s even possible to rename them.

  • Quote

    Hi all, I just noted this morning (as other seem to have previously) that I can no longer connect to privacy.  I'm using Surfshark in custom mode, which I have been for some time (other VPN providers previously).  Looking at the logs it seems vpn is connecting, it gets an IP and I think it's doing it's ping google check OK.  However testing with Firefox set to proxy to 8118 it's a fail over and over.  I did just try adding 8118 to the VPN input and output ports, but no dice. Actually not sure what those are for - couldn't find any documentation.

     

    So I understand IPTables protections have been added - can anyone link to any docs on what has changed?  Cause this isn't working for me and if not solved I'll have to try a different container.  Been a binhex fan for ages so keen to stick around if I can.

     

    Cheers.

     

    Marshalleq.

  • Quote
    36 minutes ago, Marshalleq said:

    So I understand IPTables protections have been added - can anyone link to any docs on what has changed?  Cause this isn't working for me and if not solved I'll have to try a different container.  Been a binhex fan for ages so keen to stick around if I can.

    The IPTables aren’t new.

  • Quote
    • Like 1

    Well this is about the strangest thing I have came across.  Not sure if there is actually a question in here but figured I would throw it out there just in case someone has seen something like it.  Been trying to track down something funky that has been happening. 

     

    Grab 6 linux distros and add them to deluge.  Runs for 5-10 mins and I completely lose connectivity(my whole house).  Odd, ssh into my USG, can't ping google 8.8.8.8 nothing.  K, lets disconnect the WAN cable and reconnect.  Boom, internet back up house wide....ok lets start the download again.  Same thing over and over and over again.  WTF?  

     

    So then the smart guy in me says ok download utorrent to your desktop and do the same thing.  A short while later I have 6 shiny new distros in my downloads folder.  ok...

     

    Another idea. Lets set VPN_ENABLED to no.  Fire it back up, 6 shiny new distros on my server with no issues.  

     

    This seems like a stretch but could traffic from deluge be breaking my USG somehow or could my ISP be doing something funky?

     

     

  • Quote
    3 hours ago, gzibell said:

    Well this is about the strangest thing I have came across.  Not sure if there is actually a question in here but figured I would throw it out there just in case someone has seen something like it.  Been trying to track down something funky that has been happening. 

     

    Grab 6 linux distros and add them to deluge.  Runs for 5-10 mins and I completely lose connectivity(my whole house).  Odd, ssh into my USG, can't ping google 8.8.8.8 nothing.  K, lets disconnect the WAN cable and reconnect.  Boom, internet back up house wide....ok lets start the download again.  Same thing over and over and over again.  WTF?  

     

    So then the smart guy in me says ok download utorrent to your desktop and do the same thing.  A short while later I have 6 shiny new distros in my downloads folder.  ok...

     

    Another idea. Lets set VPN_ENABLED to no.  Fire it back up, 6 shiny new distros on my server with no issues.  

     

    This seems like a stretch but could traffic from deluge be breaking my USG somehow or could my ISP be doing something funky?

     

     

     

    Sounds like an issue with your VPN provider. I would wager a guess that there are disconnection issues, retries or something of the sort. Have you checked logs? The first stop every single time is to look at your appdata logs of the container. Is your VPN provider getting blocked by IPS/IDS and/or DNS lists?

  • Quote

    Hi All 

    I could really use some help. My docker is up and running , I can hit the web UI i can add torrents but for some reason the files aren't downloading . This is the first time in years I've had this issue , I have attached the log hoping some one could help me. 

    Deluge.txt

  • Quote
    • Author
    12 hours ago, gzibell said:

    Grab 6 linux distros and add them to deluge.  Runs for 5-10 mins and I completely lose connectivity(my whole house).  Odd, ssh into my USG, can't ping google 8.8.8.8 nothing.  K, lets disconnect the WAN cable and reconnect.  Boom, internet back up house wide....ok lets start the download again.  Same thing over and over and over again.  WTF?  

     

    i would suspect the USG cannot cope with the amount of encrypted traffic, its probably attempting to analyze the encrypted traffic and cannot and this is maxing out the CPU causing total loss of internet connectivity, ive seen this with other routers, typically consumer grade, pfsense/opnsense do not generally suffer this issue, as the hardware specs are such that it can cope with multi gigabit encrypted traffic no problems.

     

    try throttling the download speed in deluge and also reduce the number of connections in deluge, if this gives you a more stable experience then you know its traffic related.

     

    you might also want to take a look and see if there are any firmware updates for your device, this could be a bug in the firmware.

  • Quote
    • Author
    6 hours ago, Evolamor said:

    Hi All 

    I could really use some help. My docker is up and running , I can hit the web UI i can add torrents but for some reason the files aren't downloading . This is the first time in years I've had this issue , I have attached the log hoping some one could help me. 

    Deluge.txt 16.71 kB · 3 downloads

    yep thats a clean log as i expected, i think your issue is probably related to where deluge is writing to, check the path for incomplete and completed and ensure no issues, to verify this is the issue TEMPORARILY set incomplete to /tmp if the download starts then you know its filesystem related (low disk space, corruption, unmounted volume).

  • Quote

    I think the PGID default port is written incorrectly as 99. I assume thats just in the definition and isn’t actually the default?

  • Quote
    • Author
    7 hours ago, Marshalleq said:

    I think the PGID default port is written incorrectly as 99. I assume thats just in the definition and isn’t actually the default?

    thanks there was some copy/pasting going on there so missed that :-), the default group is '100', btw its not a port its a 'group id'.

  • Quote


    Hello..  Started to receive a network error this morning and wanted to see if I was the only one.  GUI no longer connects after working nonstop for a few years.  Has anything changed?  I tried a few different PIA DNS servers but no success.

     

    Thanks for any help

     

     

    ____________________________________________________________________________________________________

     

      

    Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2021-11-05 05:07:02.735709 [info] Host is running unRAID
2021-11-05 05:07:02.754610 [info] System information Linux 3be0b24c9ad8 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux
2021-11-05 05:07:02.777898 [info] OS_ARCH defined as 'x86-64'
2021-11-05 05:07:02.800370 [info] PUID defined as '99'
2021-11-05 05:07:02.838791 [info] PGID defined as '100'
2021-11-05 05:07:02.891200 [info] UMASK defined as '000'
2021-11-05 05:07:02.911622 [info] Permissions already set for volume mappings
2021-11-05 05:07:02.944129 [info] Deleting files in /tmp (non recursive)...
2021-11-05 05:07:02.968962 [info] VPN_ENABLED defined as 'yes'
2021-11-05 05:07:02.989930 [info] VPN_CLIENT defined as 'openvpn'
2021-11-05 05:07:03.010404 [info] VPN_PROV defined as 'pia'
2021-11-05 05:07:03.158229 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/Czech Republic.ovpn
2021-11-05 05:07:03.199427 [info] VPN remote server(s) defined as 'czech.privacy.network,'
2021-11-05 05:07:03.216710 [info] VPN remote port(s) defined as '1198,'
2021-11-05 05:07:03.233887 [info] VPN remote protcol(s) defined as 'udp,'
2021-11-05 05:07:03.254197 [info] VPN_DEVICE_TYPE defined as 'tun0'
2021-11-05 05:07:03.274290 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2021-11-05 05:07:03.296416 [info] LAN_NETWORK defined as '192.168.1.0/24'
2021-11-05 05:07:03.317205 [info] NAME_SERVERS defined as '10.0.0.242,10.0.0.243'
2021-11-05 05:07:03.337587 [info] VPN_USER defined as '*****'
2021-11-05 05:07:03.358686 [info] VPN_PASS defined as '*******'
2021-11-05 05:07:03.379035 [info] STRICT_PORT_FORWARD defined as 'yes'
2021-11-05 05:07:03.399482 [info] ENABLE_PRIVOXY defined as 'yes'
2021-11-05 05:07:03.423988 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2021-11-05 05:07:03.443900 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2021-11-05 05:07:03.466204 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2021-11-05 05:07:03.486555 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2021-11-05 05:07:03.507682 [info] Starting Supervisor...
2021-11-05 05:07:03,777 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2021-11-05 05:07:03,777 INFO Set uid to user 0 succeeded
2021-11-05 05:07:03,781 INFO supervisord started with pid 7
2021-11-05 05:07:04,783 INFO spawned: 'shutdown-script' with pid 189
2021-11-05 05:07:04,784 INFO spawned: 'start-script' with pid 190
2021-11-05 05:07:04,785 INFO spawned: 'watchdog-script' with pid 191
2021-11-05 05:07:04,785 INFO reaped unknown pid 8 (exit status 0)
2021-11-05 05:07:04,788 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2021-11-05 05:07:04,788 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-11-05 05:07:04,788 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-11-05 05:07:04,789 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-11-05 05:07:04,826 DEBG 'start-script' stdout output:
[info] Adding 10.0.0.242 to /etc/resolv.conf

2021-11-05 05:07:04,828 DEBG 'start-script' stdout output:
[info] Adding 10.0.0.243 to /etc/resolv.conf

2021-11-05 05:07:34,864 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error


2021-11-05 05:08:09,898 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error


     

  • Quote
    • Author
    7 minutes ago, cpthook said:

    Hello..  Started to receive a network error this morning and wanted to see if I was the only one.  GUI no longer connects after working nonstop for a few years.  Has anything changed?  I tried a few different PIA DNS servers but no success.

     

    Thanks for any help

    this looks like a networking issue on your end, check your server can perform dns resolution, also check name servers 10.0.0.242,10.0.0.243 are operational.

  • Quote
    35 minutes ago, cpthook said:


    Hello..  Started to receive a network error this morning and wanted to see if I was the only one.  GUI no longer connects after working nonstop for a few years.  Has anything changed?  I tried a few different PIA DNS servers but no success.

     

    Thanks for any help

     

     

    ____________________________________________________________________________________________________

     

      

    Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2021-11-05 05:07:02.735709 [info] Host is running unRAID
2021-11-05 05:07:02.754610 [info] System information Linux 3be0b24c9ad8 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux
2021-11-05 05:07:02.777898 [info] OS_ARCH defined as 'x86-64'
2021-11-05 05:07:02.800370 [info] PUID defined as '99'
2021-11-05 05:07:02.838791 [info] PGID defined as '100'
2021-11-05 05:07:02.891200 [info] UMASK defined as '000'
2021-11-05 05:07:02.911622 [info] Permissions already set for volume mappings
2021-11-05 05:07:02.944129 [info] Deleting files in /tmp (non recursive)...
2021-11-05 05:07:02.968962 [info] VPN_ENABLED defined as 'yes'
2021-11-05 05:07:02.989930 [info] VPN_CLIENT defined as 'openvpn'
2021-11-05 05:07:03.010404 [info] VPN_PROV defined as 'pia'
2021-11-05 05:07:03.158229 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/Czech Republic.ovpn
2021-11-05 05:07:03.199427 [info] VPN remote server(s) defined as 'czech.privacy.network,'
2021-11-05 05:07:03.216710 [info] VPN remote port(s) defined as '1198,'
2021-11-05 05:07:03.233887 [info] VPN remote protcol(s) defined as 'udp,'
2021-11-05 05:07:03.254197 [info] VPN_DEVICE_TYPE defined as 'tun0'
2021-11-05 05:07:03.274290 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2021-11-05 05:07:03.296416 [info] LAN_NETWORK defined as '192.168.1.0/24'
2021-11-05 05:07:03.317205 [info] NAME_SERVERS defined as '10.0.0.242,10.0.0.243'
2021-11-05 05:07:03.337587 [info] VPN_USER defined as '*****'
2021-11-05 05:07:03.358686 [info] VPN_PASS defined as '*******'
2021-11-05 05:07:03.379035 [info] STRICT_PORT_FORWARD defined as 'yes'
2021-11-05 05:07:03.399482 [info] ENABLE_PRIVOXY defined as 'yes'
2021-11-05 05:07:03.423988 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2021-11-05 05:07:03.443900 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2021-11-05 05:07:03.466204 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2021-11-05 05:07:03.486555 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2021-11-05 05:07:03.507682 [info] Starting Supervisor...
2021-11-05 05:07:03,777 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2021-11-05 05:07:03,777 INFO Set uid to user 0 succeeded
2021-11-05 05:07:03,781 INFO supervisord started with pid 7
2021-11-05 05:07:04,783 INFO spawned: 'shutdown-script' with pid 189
2021-11-05 05:07:04,784 INFO spawned: 'start-script' with pid 190
2021-11-05 05:07:04,785 INFO spawned: 'watchdog-script' with pid 191
2021-11-05 05:07:04,785 INFO reaped unknown pid 8 (exit status 0)
2021-11-05 05:07:04,788 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2021-11-05 05:07:04,788 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-11-05 05:07:04,788 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-11-05 05:07:04,789 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-11-05 05:07:04,826 DEBG 'start-script' stdout output:
[info] Adding 10.0.0.242 to /etc/resolv.conf

2021-11-05 05:07:04,828 DEBG 'start-script' stdout output:
[info] Adding 10.0.0.243 to /etc/resolv.conf

2021-11-05 05:07:34,864 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error


2021-11-05 05:08:09,898 DEBG 'start-script' stderr output:
Error: error sending query: Could not send or receive, because of network error


     

     

    24 minutes ago, binhex said:

    this looks like a networking issue on your end, check your server can perform dns resolution, also check name servers 10.0.0.242,10.0.0.243 are operational.

    Mine started doing the exact same thing yesterday... Haven't changed a thing other then restoring a previous docker backup

     

  • Quote
    • Author
    13 minutes ago, cpthook said:

    with the SabNZBD_VPN container just fine. 

    i would suspect if you rebooted the sabnzbdvpn container it would be in the same state - i.e. unable to resolve, try changing NAME_SERVERS value to the defaults:- 

    209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1

     

  • Quote
    5 minutes ago, binhex said:

    i would suspect if you rebooted the sabnzbdvpn container it would be in the same state - i.e. unable to resolve, try changing NAME_SERVERS value to the defaults:- 

    209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1

     

     

    Thanks... :)  you are correct.  I actually just did what you suggested on my own after looking at my SAB settings again.  Looking at logs, Deluge skipped over a few name server before it chose Default route for container is 172.17.0.1.  I did not have backup name servers with my previous Deluge setup.

      

    [info] VPN is enabled, beginning configuration of VPN

2021-11-05 08:16:14,201 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-11-05 08:16:14,201 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-11-05 08:16:14,201 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-11-05 08:16:14,236 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2021-11-05 08:16:14,238 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2021-11-05 08:16:14,241 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2021-11-05 08:16:14,244 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2021-11-05 08:16:14,246 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2021-11-05 08:16:14,250 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2021-11-05 08:16:14,253 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2021-11-05 08:16:14,256 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2021-11-05 08:16:59,501 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2021-11-05 08:16:59,511 DEBG 'start-script' stdout output:
[info] Docker network defined as 172.17.0.0/16

2021-11-05 08:16:59,514 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2021-11-05 08:16:59,515 DEBG 'start-script' stdout output:
[info] ip route defined as follows...

     

  • Quote

    • Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Reply to this topic...
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.