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 - qBittorrentVPN

binhex
in Docker Containers

Featured Replies

1 hour ago, wgstarks said:

Simplest thing to do would be to revert to the previous tag as others have mentioned above.

How do i revert this in unraid? i havent rolled back to a previous one before.

  • Quote
    • Replies 5.2k
    • Views 1.1m
    • Created
    • Last Reply

    Top Posters In This Topic

    Popular Days

    Most Popular Posts

    • ulkesh
      ulkesh

      I rolled back to tag 5.1.1-1-01 which fixed the issue for me. I guess the new update wasn't tested for wireguard connections. Edit the docker container and change "Repository" from binhex/arch-qbitt

    • nraygun
      nraygun

      FWIW, I found this method in Reddit that seemed to work for me until they fix the log bug. But note if you have qbittorrent internet facing, it's a risk.   Add this line under [Preferences]

    • gustyScanner
      gustyScanner

      Hello! I have been using wireguard successfully for a long time with this container, today though when the container restarted I got the following error: 2025-06-27 10:35:26,490 DEBG 'start-script'

    Posted Images

    59 minutes ago, Tpole said:

    How do i revert this in unraid? i havent rolled back to a previous one before.

    binhex/arch-qbittorrentvpn:4.6.5-1-05

     

    Edit the container and put that into the repository. Usually it says "binhex/arch-qbittorrentvpn:latest" latest means the latest update available, instead we give it "4.6.5-1-05" meaning that version number.

     

    Quick and dirty it all means developer:container:version.

    Edited by Yock

  • Quote

    My deluge suddently not working. I get this error in the log:

     

    Error: error sending query: Error creating socket

     

    I have tried with qbittorrent too - the same problem.

     

    I'm using PIA.

     

    Anyone know what the problem is? I haven't changed any settings at all...

  • Quote

    I am unable to launch the Web UI since the most recent update

    logs.txt

  • Quote
    48 minutes ago, jrsummers said:

    I am unable to launch the Web UI since the most recent update

    Read the posts above yours

     

  • Quote
    • Author

    i'm aware of the issue guys and i think i have a fix, i shall post back when i have built a fixed image.

  • Quote
    • Author

    I'm awaiting feedback from users on github, in the meantime can anybody with the name server issue try out tagged `latest` or `4.6.5-1-07` and let me know if it fixes the issue.

    Note: This is for qbittorrentvpn ONLY.

  • Quote
    • Thanks 1
    1 hour ago, binhex said:

    I'm awaiting feedback from users on github, in the meantime can anybody with the name server issue try out tagged `latest` or `4.6.5-1-07` and let me know if it fixes the issue.

    Note: This is for qbittorrentvpn ONLY.

    The latest is now up and running without issue.  Thank you!!

  • Quote

    I'm still experiencing the issue after the latest, it works fine if I switch network to bridge rather than my VPN tunnel but has completely stopped working for my tunnel connection (this tunnel is working fine on the other apps which use it)

  • Quote
    • Author
    17 minutes ago, jrsummers said:

    if I switch network to bridge rather than my VPN tunnel

    can you explain what you mean by VPN tunnel? do you mean unraid wireguard tunnel, or sharing a vpn network with another container, or something else?

  • Quote

    it was the unraid built in wireguard tunnel, I have added a new tunnel to unraid and set that to qbittorrent and it is working again, not sure why this has fixed it but it has

  • Quote
    3 hours ago, binhex said:

    I'm awaiting feedback from users on github, in the meantime can anybody with the name server issue try out tagged `latest` or `4.6.5-1-07` and let me know if it fixes the issue.

    Note: This is for qbittorrentvpn ONLY.

     

    Looks good on my end now, Thanks binhex for a quick and prompt fix!

    (note: my issue was "error creating socket" when using a custom docker network)

     

  • Quote

    I pulled the latest and it fixed my error too. Thanks Binhex!

    Is this still the right name servers?

    - NAME_SERVERS=84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1

  • Quote

    Hello, I am new to unraid and I just got binhex-qbittorrentvpn running, I have vpn unlimited and put the config file from the instructions in this thread regarding exporting them from the vpn unlimited site, renaming it as vg0.conf and putting the file in the wireguard folder . But for some reason I cannot get to connect and the torrent keeps saying STALLED.

     

    This is my config file

     

    [Interface]
    PostUp = '/root/wireguardup.sh'
    PostDown = '/root/wireguarddown.sh'
    PrivateKey = MYKEY FROM VPN UNLIMITED
    Address = 10.103.231.254/32
    DNS = 10.100.0.1

    PreDown = powershell -command "$wgInterface = Get-NetAdapter -Name %WIREGUARD\_TUNNEL\_NAME%; route delete 0.0.0.0 mask 0.0.0.0 0.0.0.0 if $wgInterface.ifIndex metric 95"
    Table = off

    [Peer]
    PublicKey = GENERATED BY WIREGUARD
    PresharedKey = GENERATED BY WIREGUARD
    AllowedIPs = 0.0.0.0/0
    Endpoint = 184.75.208.34:259
    PersistentKeepalive = 25
     

    I appreciate any pointers here. Thanks.

  • Quote
    On 3/22/2024 at 1:21 AM, binhex said:

    Correct

    Sent from my 22021211RG using Tapatalk
     

    Once unRaid 7 comes out, we can revert to using the regular Qbittorrent with libtorrentv2 since the kernel is going to 6.8.12, right?

    Seems like there was a kernel fix for this a while back: https://github.com/arvidn/libtorrent/issues/6952

  • Quote
    On 5/22/2024 at 5:32 PM, KevinE said:

    Setting Up myanonamouse.net seedbox for use with qbt  over VPN

     

    I need to execute this command with the session id created with my vpn ip:

    sudo curl -c /path/docker/persists/mam.cookies -b 'mam_id=IP_session_cookie' https://t.myanonamouse.net/json/dynamicSeedbox.php

     

    What do I enter for the path to mam.cookies?

     

     

     

    Here's how I did it. I installed the User Script plugin, then I added a script with the following: 

    #! /bin/bash
docker exec binhex-qbittorrentvpn curl -c /path/docker/persists/mam.cookies -b '__YOUR_MAM_SESSION__' https://t.myanonamouse.net/json/dynamicSeedbox.php

     

    Then I set it up to run on a schedule, right from the User Scipts page. This tells Unraid to run the curl command inside the binhex qBittorrent container. You could also run it at any other interval, but I didn't think anything more frequent than daily was needed. Obviously, you need to replace the correct part with your MAM session.

  • Quote
    • Author
    On 7/5/2024 at 6:58 PM, bumperjeep said:

    I pulled the latest and it fixed my error too. Thanks Binhex!

    Is this still the right name servers?

    - NAME_SERVERS=84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1

    those are the defaults, yep

  • Quote
    On 7/5/2024 at 10:39 AM, binhex said:

    I'm awaiting feedback from users on github, in the meantime can anybody with the name server issue try out tagged `latest` or `4.6.5-1-07` and let me know if it fixes the issue.

    Note: This is for qbittorrentvpn ONLY.

    I had the issue, went back to previous version and no issues. Just tried to go back to latest again as per your instructions and still getting "Error: error sending query: Error creating socket". This is qbittorrentvpn with PIA WireGuard.

     

    :4.6.5-1-05 is still working just fine.

    Edited by CanadianBear

  • Quote
    • Author
    51 minutes ago, CanadianBear said:

    I had the issue, went back to previous version and no issues. Just tried to go back to latest again as per your instructions and still getting "Error: error sending query: Error creating socket". This is qbittorrentvpn with PIA WireGuard.

     

    :4.6.5-1-05 is still working just fine.

    Did you click on force update after setting the tag to latest?

  • Quote
    • Upvote 1

    I think I may be having the same issue since updating as I noticed a few days ago that my container doesn't seem to work anymore.

     

    I am using NordVPN via OpenVPN.

     

     

    Here are my logs:
      

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

2024-07-08 09:24:30.043949 [info] Host is running unRAID
2024-07-08 09:24:30.060637 [info] System information Linux 462b379bf214 6.1.79-Unraid #1 SMP PREEMPT_DYNAMIC Fri Mar 29 13:34:03 PDT 2024 x86_64 GNU/Linux
2024-07-08 09:24:30.080912 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no'
2024-07-08 09:24:30.098374 [info] PUID defined as '99'
2024-07-08 09:24:30.116646 [info] PGID defined as '100'
2024-07-08 09:24:30.165553 [info] UMASK defined as '000'
2024-07-08 09:24:30.181958 [info] Permissions already set for '/config'
2024-07-08 09:24:30.199520 [info] Deleting files in /tmp (non recursive)...
2024-07-08 09:24:30.222144 [info] VPN_ENABLED defined as 'yes'
2024-07-08 09:24:30.247245 [info] VPN_CLIENT defined as 'openvpn'
2024-07-08 09:24:30.264501 [info] VPN_PROV defined as 'airvpn'
2024-07-08 09:24:30.287761 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/uk1602.nordvpn.com.tcp443.ovpn
2024-07-08 09:24:30.325298 [info] VPN remote server(s) defined as '81.19.214.131,'
2024-07-08 09:24:30.341758 [info] VPN remote port(s) defined as '443,'
2024-07-08 09:24:30.358064 [info] VPN remote protcol(s) defined as 'tcp-client,'
2024-07-08 09:24:30.374996 [info] VPN_DEVICE_TYPE defined as 'tun0'
2024-07-08 09:24:30.394044 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2024-07-08 09:24:30.410960 [info] NAME_SERVERS defined as '84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
2024-07-08 09:24:30.608977 [info] LAN_NETWORK defined as '192.168.1.0/24'
2024-07-08 09:24:30.637095 [info] LAN_NETWORK exported as '192.168.1.0/24'
2024-07-08 09:24:30.659444 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2024-07-08 09:24:30.676259 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2024-07-08 09:24:30.693760 [info] ENABLE_STARTUP_SCRIPTS not defined (via -e ENABLE_STARTUP_SCRIPTS), defaulting to 'no'
2024-07-08 09:24:30.713365 [warn] ENABLE_SOCKS not defined (via -e ENABLE_SOCKS), defaulting to 'no'
2024-07-08 09:24:30.729874 [info] ENABLE_PRIVOXY defined as 'no'
2024-07-08 09:24:30.750105 [info] WEBUI_PORT defined as '8088'
2024-07-08 09:24:30.773007 [info] Starting Supervisor...
2024-07-08 09:24:30,888 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2024-07-08 09:24:30,888 INFO Set uid to user 0 succeeded
2024-07-08 09:24:30,889 INFO supervisord started with pid 7
2024-07-08 09:24:31,891 INFO spawned: 'start-script' with pid 272
2024-07-08 09:24:31,893 INFO spawned: 'watchdog-script' with pid 273
2024-07-08 09:24:31,893 INFO reaped unknown pid 8 (exit status 0)
2024-07-08 09:24:31,896 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2024-07-08 09:24:31,896 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-07-08 09:24:31,896 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-07-08 09:24:32,077 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via adapter eth0

2024-07-08 09:24:32,078 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2024-07-08 09:24:32,079 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0 
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.3 
192.168.1.0/24 via 172.17.0.1 dev eth0 
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 
local 172.17.0.3 dev eth0 table local proto kernel scope host src 172.17.0.3 
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.3 

2024-07-08 09:24:32,079 DEBG 'start-script' stdout output:
--------------------

2024-07-08 09:24:32,082 DEBG 'start-script' stdout output:
iptable_mangle         16384  2
ip_tables              28672  5 iptable_filter,iptable_nat,iptable_mangle
x_tables               45056  17 ip6table_filter,xt_conntrack,iptable_filter,ip6table_nat,nft_compat,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,ip6_tables,ipt_REJECT,ip_tables,iptable_nat,ip6table_mangle,xt_MASQUERADE,iptable_mangle,xt_mark

2024-07-08 09:24:32,083 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2024-07-08 09:24:32,124 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2024-07-08 09:24:32,125 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 81.19.214.131/32 -i eth0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -s 81.19.214.131/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8088 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8088 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i tun0 -j ACCEPT
-A OUTPUT -d 81.19.214.131/32 -o eth0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -d 81.19.214.131/32 -o eth0 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8088 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 8088 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT

2024-07-08 09:24:32,126 DEBG 'start-script' stdout output:
--------------------

2024-07-08 09:24:32,126 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2024-07-08 09:24:32,132 DEBG 'start-script' stdout output:
2024-07-08 09:24:32 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations. 
2024-07-08 09:24:32 Note: '--allow-compression' is not set to 'no', disabling data channel offload.

2024-07-08 09:24:32,132 DEBG 'start-script' stdout output:
2024-07-08 09:24:32 WARNING: file 'credentials.conf' is group or others accessible
2024-07-08 09:24:32 OpenVPN 2.6.11 [git:makepkg/ddf6bf6d2a135835+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Jun 20 2024
2024-07-08 09:24:32 library versions: OpenSSL 3.3.1 4 Jun 2024, LZO 2.10
2024-07-08 09:24:32 DCO version: N/A

2024-07-08 09:24:32,132 DEBG 'start-script' stdout output:
2024-07-08 09:24:32 WARNING: --ping should normally be used with --ping-restart or --ping-exit
2024-07-08 09:24:32 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2024-07-08 09:24:32 NOTE: --fast-io is disabled since we are not using UDP

2024-07-08 09:24:32,133 DEBG 'start-script' stdout output:
2024-07-08 09:24:32 TCP/UDP: Preserving recently used remote address: [AF_INET]81.19.214.131:443
2024-07-08 09:24:32 Socket Buffers: R=[87380->87380] S=[65536->65536]

2024-07-08 09:24:32,133 DEBG 'start-script' stdout output:
2024-07-08 09:24:32 Attempting to establish TCP connection with [AF_INET]81.19.214.131:443

2024-07-08 09:24:32,160 DEBG 'start-script' stdout output:
2024-07-08 09:24:32 TCP connection established with [AF_INET]81.19.214.131:443
2024-07-08 09:24:32 TCPv4_CLIENT link local: (not bound)
2024-07-08 09:24:32 TCPv4_CLIENT link remote: [AF_INET]81.19.214.131:443

2024-07-08 09:24:32,200 DEBG 'start-script' stdout output:
2024-07-08 09:24:32 TLS: Initial packet from [AF_INET]81.19.214.131:443, sid=9cd2146b 9dd4e59b

2024-07-08 09:24:32,360 DEBG 'start-script' stdout output:
2024-07-08 09:24:32 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA

2024-07-08 09:24:32,360 DEBG 'start-script' stdout output:
2024-07-08 09:24:32 VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA9

2024-07-08 09:24:32,360 DEBG 'start-script' stdout output:
2024-07-08 09:24:32 VERIFY KU OK
2024-07-08 09:24:32 Validating certificate extended key usage
2024-07-08 09:24:32 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2024-07-08 09:24:32 VERIFY EKU OK
2024-07-08 09:24:32 VERIFY X509NAME OK: CN=uk1602.nordvpn.com
2024-07-08 09:24:32 VERIFY OK: depth=0, CN=uk1602.nordvpn.com

2024-07-08 09:24:32,481 DEBG 'start-script' stdout output:
2024-07-08 09:24:32 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bits RSA, signature: RSA-SHA512, peer temporary key: 253 bits X25519
2024-07-08 09:24:32 [uk1602.nordvpn.com] Peer Connection Initiated with [AF_INET]81.19.214.131:443
2024-07-08 09:24:32 TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1

2024-07-08 09:24:32,481 DEBG 'start-script' stdout output:
2024-07-08 09:24:32 TLS: tls_multi_process: initial untrusted session promoted to trusted

2024-07-08 09:24:33,564 DEBG 'start-script' stdout output:
2024-07-08 09:24:33 SENT CONTROL [uk1602.nordvpn.com]: 'PUSH_REQUEST' (status=1)

     

    I have tried using the following versions and still seem to be having no luck:

     

    • binhex/arch-qbittorrentvpn:latest
    • binhex/arch-qbittorrentvpn:4.6.5-1-05
    • binhex/arch-qbittorrentvpn:4.6.5-1-07

     

    Any help or advice would be very much appreciated.

    Edited by ArxKnight

  • Quote
    12 hours ago, binhex said:

    no you don't, no sign of dns related issues there, I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

    Hey,

     

    Please find below the requested information:

     

    Command Execution: 

    docker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='bridge'
  --privileged=true
  -e TZ="Europe/London"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Hermes"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='REDACTED'
  -e 'VPN_PASS'='REDACTED'
  -e 'VPN_PROV'='airvpn'
  -e 'VPN_CLIENT'='openvpn'
  -e 'VPN_OPTIONS'=''
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'WEBUI_PORT'='8088'
  -e 'LAN_NETWORK'='192.168.1.0/24'
  -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
  -e 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='true'
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8088]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png'
  -p '6881:6881/tcp'
  -p '6881:6881/udp'
  -p '8118:8118/tcp'
  -p '8088:8088/tcp'
  -v '/mnt/user/media/Downloads/':'/data':'rw'
  -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn:latest'

f042c9472f0f2ab46d33de469363c5a6119579e8be4797c1b710eaffe2c0cbac

     

    Supervisor Log:

     

    Edited by ArxKnight

  • Quote
    10 hours ago, binhex said:

    from your log:-
    2024-07-08 10:30:40 AUTH: Received control message: AUTH_FAIL
     

    Please see Q16 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

    Hey,

     

    I have checked the following:

     

    Cause: Your subscription has run out

    Answer: It's still valid

    Cause: You have not typed in your username (VPN_USER value) and/or password (VPN_PASS value) correctly

    Answer: I have change the password to be sure, made sure there is no whitespace in either box and also tried using my normal username/password as well as the "Service credentials (manual setup)"

    Cause: You are using the wrong credentials

    Answer: These have been tested as working as I can use the Nord desktop app by logging in and using it that way.

    Cause: Your password contains a character which may cause issues

    Answer: The new password only contains letters a-z (upper case or lower case) and numbers 0-9

    Cause: Your password is too long

    Answer: The Password is less than 99 characters

    Cause: Out of date openvpn config file (ovpn extension)

    Answer: I have changed these to ensure they are up to date (old: uk1602 new: uk1626)

    Cause: The vpn provider you have signed up with is having authentication issues

    Answer: I have sent them an email for support but I am just waiting for a reply.

     

    Could anything else be causing this do you think as it's strange that nothing was changed but it stopped working.

     

    Thanks

    Edited by ArxKnight

  • 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.