[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban) - Page 5 - Docker Containers

December 8, 20169 yr

Are there any guides or tutorials around on how to have Letsencrypt interact with my other dockers on unraid?

I understand the general concept behind Letsencrypt, but I'm not sure what files need to be modified, and how to modify these files.

My current setup is your standard dynamic IP address provided by my ISP. I have this tracked by duckdns so I can associated the IP with the static name. I'd like to be able to attach to all of my different dockers through https:

https://insertname.duckdns.org:2020 - Docker 1c

https://insertname.duckdns.org:3030 - Docker 2

https://insertname.duckdns.org:4040 - Docker 3

A few of the dockers I run now are:

crashplan

owncloud

plex

plexpy

plexrequests

couchpotato

sonarr

Any fingers to point me in the right direction would be greatly appreciated

You'll have to sort out the SSL on each of the containers you want behind the reverse proxy. If all the services are on the same Unraid box using https between them is unnecessary imo. Searching this thread....

Thanks for your help!

Sorry for being thick

Managed to get CouchPotato working using the default one and muximux as the homepage but can't seem to get other apps working

The apps I wanted were

Sonarr

PlexPy

PlexRequests

NetData

Deluge

I've tried the PlexPy command and getting a 404 error, I think this might be down to my plexpy settings though

# Sonar
# https://github.com/linuxserver/docker-sonarr
#
# Edit the settings and set 
# Url Base to /sonarr

location ^~ /sonarr {
    proxy_pass http://192.168.1.28:8989/sonarr;
    include /config/nginx/proxy.conf;
}

# PlexyPy
# https://github.com/linuxserver/docker-plexpy
#
# Settings => Web Interface
# Change http root to /plexpy
#

location ^~ /plexpy/ {
    proxy_pass http://192.168.1.28:8181;
    include /config/nginx/proxy.conf;
    proxy_bind $server_addr;
    proxy_set_header X-Forwarded-Host $server_name;
    proxy_set_header X-Forwarded-Ssl     on;
}

# PlexRequests
# https://github.com/linuxserver/docker-plexrequests
#
# Run container with -e "URL_BASE"="/plexrequests"
#

location ^~ /requests {
    proxy_pass http://192.168.1.28:3000/requests;
    include /config/nginx/proxy.conf;
}

# Deluge
# https://github.com/linuxserver/docker-deluge
#
# No extra settings required
#

location ^~ /deluge {
    proxy_pass http://192.168.1.28:8112/;
    proxy_set_header  X-Deluge-Base "/deluge/";
    include /config/nginx/proxy.conf;
}

Netdata i've never heard of, you'll have to figure that one out yourself I'm afraid.

and looking up a few posts.

Just got this docker setup for my domain, real simple thanks guys.

However, I have no experience with nginx (coming from Apache docker). Can someone point me to a good reference for how to configure this docker to redirect say my requests.domain.com to my PlexRequests docker?

Save this as requests in the same folder as default.

server {
       listen         80;
       server_name    requests.server.com;
       return         301 https://$server_name$request_uri;
}

server {
listen 443 ssl;
server_name requests.server.com;

root /config/www;
index index.html index.htm index.php;

###SSL Certificates
ssl_certificate /config/keys/letsencrypt/fullchain.pem;
ssl_certificate_key /config/keys/letsencrypt/privkey.pem;

###Diffie–Hellman key exchange ###
ssl_dhparam /config/nginx/dhparams.pem;

###SSL Ciphers
ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA';

###Extra Settings###
ssl_prefer_server_ciphers on;
ssl_session_cache shared:SSL:10m;

        ### Add HTTP Strict Transport Security ###
add_header Strict-Transport-Security "max-age=63072000; includeSubdomains";
add_header Front-End-Https on;

client_max_body_size 0;

location / {
    	proxy_pass https://192.168.0.1:3000/;
  }
}

Alternatively, paste this into default to access plexrequests at server.com/requests (You will need to set the URLBASE to /requests)

	location /requests {
	proxy_pass http://192.168.0.1:3000/requests;
	include /config/nginx/proxy.conf;
}

Obviously for both you'll need to change the IP address +/- port

We don't have an Owncloud container, but in our nextcloud support thread there are some links in the first post.

For Plex

	location /plex {
	proxy_pass http://192.168.0.1:32400/web;
	include /config/nginx/proxy.conf;
}

location /web {
	proxy_pass http://192.168.0.1:32400/web;
	include /config/nginx/proxy.conf;
}

Quote

December 9, 20169 yr

Thanks for the reply CHBMB.

I did a quick search earlier and saw those lines of code. The post was looking to see if there was more of an all encompassing type of guide on how to do this.

What file am I modifying with those lines of code? Is it some sort of .conf file within Letsencrypt?

And I'm not sure I follow what you're saying about it being unnecessary. All of the dockers are on the same unraid box. Why would using https be unnecessary if I'm trying to reach my unraid box from outside of my network? Maybe I'm misunderstanding some basic security concepts here...

Quote

December 9, 20169 yr

The file to edit is default in the /mnt/cache/nginx folder.

All the SSL to handle the outside connections is handled by this container, the communication between this container and those you want to proxy happens, in your case, all on your Unraid box.

You may want to create a .htpasswd file to password protect some of those apps.

Sent from my LG-H815 using Tapatalk

Quote

December 9, 20169 yr

Where do I place the created .htpasswd file? And what type of security does this bring to the containers?

Quote

December 9, 20169 yr

Place the .htpasswd file where it states in the configs I posted. It adds a user & password to whatever you proxy, so this is done at the level of nginx rather than whatever app you're proxying. Some apps, like Nextcloud and Plex I would still use the default app username and password with, as it integrates better and is implemented well. But for things like Couch or Sonarr, personally I would trust SSL and nginx security way more than I would whatever they implement.

Sent from my LG-H815 using Tapatalk

Quote

December 9, 20169 yr

I certainly have a very rudimentary understanding of how these dockers interact as I'm still quite confused as to what needs to be modified, and how.

For instance, if I simply want Plexypy to run through https I would:

1. Modify the nginx.conf by copy and pasting the following:

# PlexyPy

# https://github.com/linuxserver/docker-plexpy

#

# Settings => Web Interface

# Change http root to /plexpy

#

location ^~ /plexpy/ {

proxy_pass http://192.168.1.28:8181;

include /config/nginx/proxy.conf;

proxy_bind $server_addr;

proxy_set_header X-Forwarded-Host $server_name;

proxy_set_header X-Forwarded-Ssl on;

}

Then I'd also have to place an .htpasswd file in ~/plexpy/. But what are the contents of this .htpasswd file?

It looks like letsencrypt is a bit more involved then some of your more basic plug and play apps.

My goal is to be able to interact with these dockers securely from outside of my network. So to do that, I've opened each ones respective port and assumed that as long as I have https running on each open port, I should be good to go?

Maybe if there's some basic primer on how this stuff works, if someone could point me in the right direction I could do some of my own readings rather than having to ask all of these random questions and re ask them when they're answered at a level beyond my understanding :-[

Quote

December 9, 20169 yr

I certainly have a very rudimentary understanding of how these dockers interact as I'm still quite confused as to what needs to be modified, and how.

For instance, if I simply want Plexypy to run through https I would:

1. Modify the nginx.conf by copy and pasting the following:

# PlexyPy

# https://github.com/linuxserver/docker-plexpy

#

# Settings => Web Interface

# Change http root to /plexpy

#

location ^~ /plexpy/ {

proxy_pass http://192.168.1.28:8181;

include /config/nginx/proxy.conf;

proxy_bind $server_addr;

proxy_set_header X-Forwarded-Host $server_name;

proxy_set_header X-Forwarded-Ssl on;

}

Then I'd also have to place an .htpasswd file in ~/plexpy/. But what are the contents of this .htpasswd file?

It looks like letsencrypt is a bit more involved then some of your more basic plug and play apps.

My goal is to be able to interact with these dockers securely from outside of my network. So to do that, I've opened each ones respective port and assumed that as long as I have https running on each open port, I should be good to go?

Maybe if there's some basic primer on how this stuff works, if someone could point me in the right direction I could do some of my own readings rather than having to ask all of these random questions and re ask them when they're answered at a level beyond my understanding

See the description at the following link for htpasswd, you just run a single command: https://hub.docker.com/r/linuxserver/letsencrypt/

Quote

December 9, 20169 yr

I certainly have a very rudimentary understanding of how these dockers interact as I'm still quite confused as to what needs to be modified, and how.

For instance, if I simply want Plexypy to run through https I would:

1. Modify the nginx.conf by copy and pasting the following:

# PlexyPy

# https://github.com/linuxserver/docker-plexpy

#

# Settings => Web Interface

# Change http root to /plexpy

#

location ^~ /plexpy/ {

proxy_pass http://192.168.1.28:8181;

include /config/nginx/proxy.conf;

proxy_bind $server_addr;

proxy_set_header X-Forwarded-Host $server_name;

proxy_set_header X-Forwarded-Ssl on;

}

Let's look at the above as an example.

location ^~ /plexpy/

Tells the webserver that this will be located at the server.com/plexpy address

 proxy_pass http://192.168.1.28:8181;
    include /config/nginx/proxy.conf;

Tells nginx where to find the plexpy app and to use the proxy settings in the proxy.conf file

 proxy_bind $server_addr;
    proxy_set_header X-Forwarded-Host $server_name;
    proxy_set_header X-Forwarded-Ssl     on;

Tells plexpy to use some extra settings necessary to get this working. Don't worry about these, app specific settings can often be found with a bit of googling though.

auth_basic "Restricted";
auth_basic_user_file /config/.htpasswd;

Now to add password protection, you need to add the above lines to that config but you also need to create a .htpasswd file. There are instructions here in the readme or if you prefer you can use an online tool like this one.

Copying the last line of chbmb:osQXeEdll4XFk to a file called .htpasswd and placing it in the /config folder (/mnt/user/appdata/nginx or something similar) Note whatever text editor you use (NOT NOTEPAD ON WINDOWS) must use linux line endings. If you want to use multiple users then just add a new line for each user. So the linuxserver .htpasswd may end up looking like this.

username:hashedpassword Obviously this example below doesn't have real hashed passwords in...

aptalca:weneedatokenyank
asshopo:notanotheryankwhokeepswaving
chbmb:theonlysaneone
danioj:britabroaddownunder
ironicbadger:gladbadgerbaitingisillegal
j0nnymoe:toocoolforschool
kode:phpninjamaster
saarg:tokenswedishguy
smdion:wethinkhesstillalivebutnotreallysure
sparklyballs:grumpyoldman
stark:anyexcusetowearleather
squid:yumyumcouldbedinner
xe:themannoonereallyknowsexists
stark:anyexcusetowearleather

So final "block" looks like this:

location ^~ /plexpy/ {
    proxy_pass http://192.168.1.28:8181;
    include /config/nginx/proxy.conf;
    proxy_bind $server_addr;
    proxy_set_header X-Forwarded-Host $server_name;
    proxy_set_header X-Forwarded-Ssl     on;
    auth_basic "Restricted";
    auth_basic_user_file /config/.htpasswd;
}

Then I'd also have to place an .htpasswd file in ~/plexpy/. But what are the contents of this .htpasswd file?

No, you'd place .htpasswd in the /config folder. As shown in the example above.

It looks like letsencrypt is a bit more involved then some of your more basic plug and play apps.

Yes it is, has more functionality, so is more complicated, essentially it's a pretty much fully blown webserver, rather than a single app that runs on a webserver.

My goal is to be able to interact with these dockers securely from outside of my network. So to do that, I've opened each ones respective port and assumed that as long as I have https running on each open port, I should be good to go?

That's achievable and what this docker is designed for. Once you've done one or two apps, it kind of click. However you've got the above bit a little wrong. The whole point of this is so you DON'T open a ton of ports on your router. Just 80 & 443 both forwarded to your Unraid box. Then all communication with any app is proxied through the nginx container. The config out of the box will automatically forward all port 80 requests to 443, so all communication actually takes place over https and is encrypted. Now go and close those ports again!

Maybe if there's some basic primer on how this stuff works, if someone could point me in the right direction I could do some of my own readings rather than having to ask all of these random questions and re ask them when they're answered at a level beyond my understanding

It's difficult to point at one single resource. We're working on something to try and make this a bit easier but, don't worry, we'll get you going. Just bear with it.

Quote

1

December 9, 20169 yr

aptalca:weneedatokenyank
asshopo:notanotheryankwhokeepswaving
chbmb:theonlyinsaneone
danioj:britabroaddownunder
ironicbadger:gladbadgerbaitingisillegal
j0nnymoe:toocoolforschool
kode:phpninjamaster
saarg:tokenswedishguy
smdion:wethinkhesstillalivebutnotreallysure
sparklyballs:grumpyoldman
stark:anyexcusetowearleather
squid:yumyumcouldbedinner
xe:themannoonereallyknowsexists
stark:anyexcusetowearleather

;D

I'm dyin' here!

;D

Serious question, which I'm sure the internet knows but I'm too lazy to ask, what happens if you have 2 identical user names with different hashes? Do they both work? Neither? Only 1st listed? Only last?

Quote

December 9, 20169 yr

Dunno, lemme check.... $:-\$

EDIT: Only my first entry in .htpasswd worked.

Quote

December 9, 20169 yr

Dunno, lemme check.... $:-\$

EDIT: Only my first entry in .htpasswd worked.

Thanks! Teh more you know...

Quote

December 9, 20169 yr

Dunno, lemme check.... $:-\$

EDIT: Only my first entry in .htpasswd worked.

Thanks! Teh more you know...

Cheeky bugger! Just spotted what you've done!

chbmb:theonlyinsaneone
;D
I'm dyin' here!

;D

Serious question, which I'm sure the internet knows but I'm too lazy to ask, what happens if you have 2 identical user names with different hashes? Do they both work? Neither? Only 1st listed? Only last?

Quote

December 9, 20169 yr

Holy smokes. Thanks CHBMB for taking the time to write that out. I'll have time later this evening to thoroughly read through and attempt to apply what you've said. I think I have a better understanding from a brief glance. This is supposed to make the system more secure by limiting the amount of ports I'm opening.

Post #521373...

https://lime-technology.com/forum/index.php?topic=53542.msg521373#msg521373

...should be a go-to post for super n00b questions like my own.

Quote

1

December 9, 20169 yr

Holy smokes. Thanks CHBMB for taking the time to write that out. I'll have time later this evening to thoroughly read through and attempt to apply what you've said. I think I have a better understanding from a brief glance. This is supposed to make the system more secure by limiting the amount of ports I'm opening.

Post #521373...

https://lime-technology.com/forum/index.php?topic=53542.msg521373#msg521373

...should be a go-to post for super n00b questions like my own.

No problem, like I said, we'll get you there.

Quote

December 10, 20169 yr

aptalca:weneedatokenyank
asshopo:notanotheryankwhokeepswaving
chbmb:theonlyinsaneone
danioj:britabroaddownunder
ironicbadger:gladbadgerbaitingisillegal
j0nnymoe:toocoolforschool
kode:phpninjamaster
saarg:tokenswedishguy
smdion:wethinkhesstillalivebutnotreallysure
sparklyballs:grumpyoldman
stark:anyexcusetowearleather
squid:yumyumcouldbedinner
xe:themannoonereallyknowsexists
stark:anyexcusetowearleather
;D
I'm dyin' here!

;D

Serious question, which I'm sure the internet knows but I'm too lazy to ask, what happens if you have 2 identical user names with different hashes? Do they both work? Neither? Only 1st listed? Only last?

I AM NOT SWEDISH!! > :'(

Quote

December 10, 20169 yr

Denmark, Sweden, same thing...

Sent from my LG-H815 using Tapatalk

Quote

December 10, 20169 yr

aptalca:weneedatokenyank
asshopo:notanotheryankwhokeepswaving
chbmb:theonlyinsaneone
danioj:britabroaddownunder
ironicbadger:gladbadgerbaitingisillegal
j0nnymoe:toocoolforschool
kode:phpninjamaster
saarg:tokenswedishguy
smdion:wethinkhesstillalivebutnotreallysure
sparklyballs:grumpyoldman
stark:anyexcusetowearleather
squid:yumyumcouldbedinner
xe:themannoonereallyknowsexists
stark:anyexcusetowearleather
;D
I'm dyin' here!

;D

Serious question, which I'm sure the internet knows but I'm too lazy to ask, what happens if you have 2 identical user names with different hashes? Do they both work? Neither? Only 1st listed? Only last?
I AM NOT SWEDISH!! > :'(

hurdy gurdy

Quote

December 10, 20169 yr

aptalca:weneedatokenyank
asshopo:notanotheryankwhokeepswaving
chbmb:theonlyinsaneone
danioj:britabroaddownunder
ironicbadger:gladbadgerbaitingisillegal
j0nnymoe:toocoolforschool
kode:phpninjamaster
saarg:tokenswedishguy
smdion:wethinkhesstillalivebutnotreallysure
sparklyballs:grumpyoldman
stark:anyexcusetowearleather
squid:yumyumcouldbedinner
xe:themannoonereallyknowsexists
stark:anyexcusetowearleather
;D
I'm dyin' here!

;D

Serious question, which I'm sure the internet knows but I'm too lazy to ask, what happens if you have 2 identical user names with different hashes? Do they both work? Neither? Only 1st listed? Only last?
I AM NOT SWEDISH!! > :'(
hurdy gurdy

Watch your backs guys... You know I'm in Liverpool this weekend....

Quote

December 10, 20169 yr

aptalca:weneedatokenyank
asshopo:notanotheryankwhokeepswaving
chbmb:theonlyinsaneone
danioj:britabroaddownunder
ironicbadger:gladbadgerbaitingisillegal
j0nnymoe:toocoolforschool
kode:phpninjamaster
saarg:tokenswedishguy
smdion:wethinkhesstillalivebutnotreallysure
sparklyballs:grumpyoldman
stark:anyexcusetowearleather
squid:yumyumcouldbedinner
xe:themannoonereallyknowsexists
stark:anyexcusetowearleather
;D
I'm dyin' here!

;D

Serious question, which I'm sure the internet knows but I'm too lazy to ask, what happens if you have 2 identical user names with different hashes? Do they both work? Neither? Only 1st listed? Only last?
I AM NOT SWEDISH!! > :'(
hurdy gurdy
Watch your backs guys... You know I'm in Liverpool this weekend....

cool, i was in liverpool last weekend, one of the christmas market stalls was selling swedish fish...

Quote

December 10, 20169 yr

aptalca:weneedatokenyank
asshopo:notanotheryankwhokeepswaving
chbmb:theonlyinsaneone
danioj:britabroaddownunder
ironicbadger:gladbadgerbaitingisillegal
j0nnymoe:toocoolforschool
kode:phpninjamaster
saarg:tokenswedishguy
smdion:wethinkhesstillalivebutnotreallysure
sparklyballs:grumpyoldman
stark:anyexcusetowearleather
squid:yumyumcouldbedinner
xe:themannoonereallyknowsexists
stark:anyexcusetowearleather
;D
I'm dyin' here!

;D

Serious question, which I'm sure the internet knows but I'm too lazy to ask, what happens if you have 2 identical user names with different hashes? Do they both work? Neither? Only 1st listed? Only last?
I AM NOT SWEDISH!! > :'(
hurdy gurdy
Watch your backs guys... You know I'm in Liverpool this weekend....
cool, i was in liverpool last weekend, one of the christmas market stalls was selling swedish fish...

I'm so disappointed now.... $:-\$ No Christmas cards for you guys! No pøpcørn for you either

Quote

December 10, 20169 yr

So I think I have everything right on the Letsencrypt end, as myserver.com/plexpy is getting a the green lock on chrome for https acceptance, but it's taking me to a 404 not found screen.

When my plexpy settings are this:

I get this:

Inside my nginix/site-confs/default my code is:

location ^~ /plexpy {
	proxy_pass http://192.168.1.3:8181;
	include /config/nginx/proxy.conf;
	proxy_bind $server_addr;
	proxy_set_header X-Forwarded-Host $server_name;
	proxy_set_header X-Forwarded-Ssl     on;
	auth_basic "Restricted";
	auth_basic_user_file /config/.htpasswd;

And on check, if I go to http://192.168.1.3:8181 I get taken directly to the plexpy home.

Any ideas where I'm going wrong? I think I'm close!

Quote

December 10, 20169 yr

So I think I have everything right on the Letsencrypt end, as myserver.com/plexpy is getting a the green lock on chrome for https acceptance, but it's taking me to a 404 not found screen.

When my plexpy settings are this:

I get this:

Inside my nginix/site-confs/default my code is:
location ^~ /plexpy {
	proxy_pass http://192.168.1.3:8181;
	include /config/nginx/proxy.conf;
	proxy_bind $server_addr;
	proxy_set_header X-Forwarded-Host $server_name;
	proxy_set_header X-Forwarded-Ssl     on;
	auth_basic "Restricted";
	auth_basic_user_file /config/.htpasswd;
And on check, if I go to http://192.168.1.3:8181 I get taken directly to the plexpy home.

Any ideas where I'm going wrong? I think I'm close!

Didn't follow the instructions

Change http root to /plexpy

# PlexyPy
# https://github.com/linuxserver/docker-plexpy
#
# Settings => Web Interface
# Change http root to /plexpy
#

location ^~ /plexpy/ {
    proxy_pass http://192.168.1.28:8181;
    include /config/nginx/proxy.conf;
    proxy_bind $server_addr;
    proxy_set_header X-Forwarded-Host $server_name;
    proxy_set_header X-Forwarded-Ssl     on;
}

Quote

December 10, 20169 yr

Ahh, the comments! Always miss something.

However, now I have a new error:

when I type in https://myserver.com/plexpy it redirects me to https://_/plexpy/auth/logout and I get this message.

Quote

December 10, 20169 yr

Ahh, the comments! Always miss something.

However, now I have a new error:

when I type in https://myserver.com/plexpy it redirects me to https://_/plexpy/auth/logout and I get this message.

Looking at the config you posted you're missing a trailing slash.

location ^~ /plexpy {

vs

location ^~ /plexpy/ {

Also, can you actually hit https://www.server.com as it looks like there's no DNS record for it.

Quote

December 10, 20169 yr

Going to https://server.com brings me to the index.html page created by letsencrypt:

I added the trailing slash:

location ^~ /plexpy/ {
	proxy_pass http://192.168.1.3:8181;
	include /config/nginx/proxy.conf;
	proxy_bind $server_addr;
	proxy_set_header X-Forwarded-Host $server_name;
	proxy_set_header X-Forwarded-Ssl     on;
	auth_basic "Restricted";
	auth_basic_user_file /config/.htpasswd;

I'm still brought to:

I've also noticed, once I make those two changes to the settings, to enable the proxy and add /plexpy, I can no longer access Plexpy through the web GUI.

EDIT: Just ran a quick test. The checkbox for "Enable for HTTP Proxy" works. I can check this and restart without an issue. It's once I add /plexpy and restart that I can no longer access the GUI.

Quote

[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

Featured Replies

Top Posters In This Topic

Popular Days

Most Popular Posts

nraygun

aptalca

BigBoyMarky

Posted Images

Join the conversation

Top Posters In This Topic

Popular Days

Most Popular Posts

nraygun

aptalca

BigBoyMarky

Posted Images

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)