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] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

Featured Replies

This seems to have worked. I edited nothing, just made the docker again and moved the files over.

  • Replies 6.2k
  • Views 1.5m
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Confirming this worked for me too. Not sure I needed to replace both, but I did anyway and Swag and Nextcloud are both back and up and running. For noobs like me, here's what I did: 1. Stop

  • I will only post this once. Feel free to refer folks to this post.   A few points of clarification:   The last update of this image didn't break things. Letsencrypt abruptly disabl

  • BigBoyMarky
    BigBoyMarky

    I replaced both the ssl.conf and nginx.conf files with the sample ones to update them since I did not make any custom modifications to either one of those and this resolved my issue.

Posted Images

Hey thanks for this docker. I just moved everything over from the Apache docker to get https. Everything moved over find apart from my media wiki install. Running the existing install or a new install throws this error page. It states that php is missing XML and iconv. I know that you stated that you left some surplus packages out of this php install to reduce on size but was a little surprised by the XML package being missing.

 

Not sure how pressed you are for size but in theory if you made the php5 folder available people could include the missing packages as *.so files in the php.ini file to keep them out of the docker image.

Hey thanks for this docker. I just moved everything over from the Apache docker to get https. Everything moved over find apart from my media wiki install. Running the existing install or a new install throws this error page. It states that php is missing XML and iconv. I know that you stated that you left some surplus packages out of this php install to reduce on size but was a little surprised by the XML package being missing.

 

Not sure how pressed you are for size but in theory if you made the php5 folder available people could include the missing packages as *.so files in the php.ini file to keep them out of the docker image.

We'll add them

I have enabled http2 on my server as well as removing tls1.0 as I have read it is not seen as secure while also trying to create a strong dh pem named dhparams-4096.pem

 

I changed my default file to point to the new file, but noted in the log that a new dhparams was created using the lesser 2048 on restart.

 

Is there a place to edit the dh file that gets created that I can edit to get 4096?

 

Thanks in advance

I have enabled http2 on my server as well as removing tls1.0 as I have read it is not seen as secure while also trying to create a strong dh pem named dhparams-4096.pem

 

I changed my default file to point to the new file, but noted in the log that a new dhparams was created using the lesser 2048 on restart.

 

Is there a place to edit the dh file that gets created that I can edit to get 4096?

 

Thanks in advance

 

https://github.com/linuxserver/docker-letsencrypt#parameters

 

Oops, got it, thanks :)

Has anyone configured their default file for the COPS calibre docker?  If so I would like suggestions on what to try.  I got several other dockers working based on suggestions in this thread.

 

Here is what I tried:

location ^~ /cops {
	auth_basic "Restricted";
	auth_basic_user_file /config/nginx/.htpasswd;
	include /config/nginx/proxy.conf;
	proxy_pass http://192.168.0.50:85;
}

 

This is all new to me and the confusing part is the URLBase changes.  I see how some dockers like sonarr and htpc manager have settings within the docker....but others don't so I am not sure what to do.

 

Also how are most people using this..for example do you create an index.html page with links to each of your web interfaces to the dockers you are trying to reach?  If so do you keep the "landing" page open to the public and then when you click the link to the docker...then it goes to https???  The reason I am asking is that I would like to have www.mydomain.com be open to the public with a link to a public photo gallery (using an unraid docker...haven't picked one yet) and then have some other page with hyperlinks to my hidden docker management tools.

 

Thanks in advance for any help you can provide.

 

Dan

 

 

I think most of us are using either self-coded landing pages or something like Muximux, Organizr, IDashboard-PHP, etc.

html5up.net has awesome free html5 templates. I grabbed and modified one to be my landing page

Those html5 templates are awesome...thanks for the recommendation.

 

Just curious...what are you using to edit them?  Do you have a recommended freeware html editor....or are you just using a text editor such as Notepad++

 

Thanks,

 

Dan

Those html5 templates are awesome...thanks for the recommendation.

 

Just curious...what are you using to edit them?  Do you have a recommended freeware html editor....or are you just using a text editor such as Notepad++

 

Thanks,

 

Dan

I use notepad++

Any suggestions on how to integrate Piwigo and COPS dockers to the reverse proxy?

 

Thanks,

 

Dan

On a fresh install of this docker im getting the followig error:

 

Nginx: [emerg] BIO_new_file("/config/keys/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/config/keys/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)

 

Any ideas?

 

Edit: my conf mistake. Nvm

A wee bit of a warning when you make a big change (PHP5 to PHP7) would be cool  ;D

A wee bit of a warning when you make a big change (PHP5 to PHP7) would be cool  ;D

 

Fair point... our bad.  :-[

 

However, we can't post the same information in multiple places as it's a logistical nightmare with every container, if you want to see if an update brings any big changes then the links on the first post will take you to the Github page and the readme there will have any changes listed.

A wee bit of a warning when you make a big change (PHP5 to PHP7) would be cool  ;D

 

Fair point... our bad.  :-[

 

However, we can't post the same information in multiple places as it's a logistical nightmare with every container, if you want to see if an update brings any big changes then the links on the first post will take you to the Github page and the readme there will have any changes listed.

 

Ya, I get it. I mostly blame myself for blindly updating. I need to stop doing that.

A wee bit of a warning when you make a big change (PHP5 to PHP7) would be cool  ;D

 

Fair point... our bad.  :-[

 

However, we can't post the same information in multiple places as it's a logistical nightmare with every container, if you want to see if an update brings any big changes then the links on the first post will take you to the Github page and the readme there will have any changes listed.

 

Ya, I get it. I mostly blame myself for blindly updating. I need to stop doing that.

 

Don't blame yourself, even I blindly update our containers...  ;D

Don't blame yourself, even I blindly update our containers...  ;D

 

Surely because you have a blind trust in your own product do you not?  ;D

Don't blame yourself, even I blindly update our containers...  ;D

 

Surely because you have a blind trust in your own product do you not?  ;D

 

Exactly....  8)

Don't blame yourself, even I blindly update our containers...  ;D

 

Here's a question. Can I restore my docker container from before my update? or will that cause problems? It would buy me time to have to deal with this change when I actually have some time to spare  :D

Don't blame yourself, even I blindly update our containers...  ;D

 

Here's a question. Can I restore my docker container from before my update? or will that cause problems? It would buy me time to have to deal with this change when I actually have some time to spare  :D

 

Yeah try tagging 32, 33 or something earlier.

 

So change the repository to linuxserver/letsencrypt:32

Don't blame yourself, even I blindly update our containers...  ;D

 

Here's a question. Can I restore my docker container from before my update? or will that cause problems? It would buy me time to have to deal with this change when I actually have some time to spare  :D

 

Yeah try tagging 32, 33 or something earlier.

 

So change the repository to linuxserver/letsencrypt:32

 

Oohhh nice. That worked. Thank you sir!

Just out of curiosity, what did php7 break?

(I'm not a php guy)

 

PHPBB Forums prior to 3.2 (just released a month ago) only supported PHP5. I'm still on 3.1.10 and haven't upgraded yet. Reason being is that I'm waiting for the themes/extensions to be updated before I do so. When I updated this docker without realizing and then seeing the errors, I tried just updating to 3.2 but it wasn't working, likely missing some modules. the 3.2 installation instructions mentions some additional PHP modules needed to run the new version.

 

So, when I do get around to updating my forum, don't be surprised if I come begging for a couple of PHP7 modules to be added  ;D

 

Thanks guys. I do appreciate the work you put in.

I just updated and I keep getting "undefined function session_start()" for one of my sites. Was this compiled with --disable-session?

 

 

EDIT: Nevermind, I see with php -i

"Session Support => enabled"

Not sure why I'm getting this error.

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

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.