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

[blaine07]

after i port forwarded to tcp 80 and 443 i get this screen. I have input the password and it does not go in. 
 
 

Theirs a Nextcloud file too that has to be edited; did you already edit it?

Sent from my SM-G975U using Tapatalk

[blaine07]

Whatever your issue is at this point may be a Nextcloud issue though. Might search through Ndxtcloud support thread for ideas too

Sent from my SM-G975U using Tapatalk

[Tucubanito07]

4 minutes ago, blaine07 said:

Theirs a Nextcloud file too that has to be edited; did you already edit it?

Sent from my SM-G975U using Tapatalk
 

Here is the screen shot.

[blaine07]

Here is the screen shot.

I'd have to look at mine in a bit to make any sense of it

Sent from my SM-G975U using Tapatalk

[Tucubanito07]

1 minute ago, blaine07 said:

I'd have to look at mine in a bit to make any sense of it

Sent from my SM-G975U using Tapatalk
 

Thank you @blaine07

[blaine07]

Thank you [mention=88940]blaine07[/mention]

That file has Nextcloud as using port 444? Thought you were forwarding 80 and 443?

Sent from my SM-G975U using Tapatalk

[Tucubanito07]

36 minutes ago, blaine07 said:

That file has Nextcloud as using port 444? Thought you were forwarding 80 and 443?

Sent from my SM-G975U using Tapatalk
 

On the router I am forwarding external 80 to intel 81 and external 443 to internal 444

Edited May 29, 2019 by Tucubanito07

[saarg]

1 hour ago, Tucubanito07 said:

On the router I am forwarding external 80 to intel 81 and external 443 to internal 444

You are directing 443 directly to your nextcloud. You use 442 for letsencrypt. So change the 443 port forwarding to 442.

[Tucubanito07]

25 minutes ago, saarg said:

You are directing 443 directly to your nextcloud. You use 442 for letsencrypt. So change the 443 port forwarding to 442.

You mean like this in the router settings?

 

 

[ijuarez]

20 minutes ago, Tucubanito07 said:

You mean like this in the router settings?

 

 

yes

 

[saarg]

1 hour ago, ijuarez said:

yes

 

No!

443 external to 442 internal.

 

Edited May 29, 2019 by saarg
Internal kernel panic. Brain said 442, but flingers didn't agree!

[Tucubanito07]

6 minutes ago, saarg said:

No!

443 external to 443 internal.

I am in the middle of watching the spaceinvader video again and re-doing everything to see if is something i missed. Lets see how this goes.

[gacpac]

I am in the middle of watching the spaceinvader video again and re-doing everything to see if is something i missed. Lets see how this goes.

PM me

Sent from my Pixel 2 XL using Tapatalk

[Tucubanito07]

37 minutes ago, saarg said:

No!

443 external to 443 internal.

I am getting this when i start lets encrypt.

 

nginx: [emerg] PEM_read_bio_DHparams("/config/nginx/dhparams.pem") failed (SSL: error:0909006C:PEM routines:get_name:no start line:Expecting: DH PARAMETERS)
Server ready
nginx: [emerg] PEM_read_bio_DHparams("/config/nginx/dhparams.pem") failed (SSL: error:0909006C:PEM routines:get_name:no start line:Expecting: DH PARAMETERS)

[Tucubanito07]

I am using No-IP container in Unraid. I got the confirmation that is working. @saarg

 

[saarg]

1 minute ago, Tucubanito07 said:

I am using No-IP container in Unraid. I got the confirmation that is working. @saarg

 

I don't know what you mean by email and noip.

See my edit on the port forwarding. I made a typo of the big type.

[Tucubanito07]

Just now, saarg said:

I don't know what you mean by email and noip.

See my edit on the port forwarding. I made a typo of the big type.

The email address that for No-IP to verify your account for No-IP. I am getting this error. @saarg

 

nginx: [emerg] PEM_read_bio_DHparams("/config/nginx/dhparams.pem") failed (SSL: error:0909006C:PEM routines:get_name:no start line:Expecting: DH PARAMETERS)

[saarg]

2 minutes ago, Tucubanito07 said:

The email address that for No-IP to verify your account for No-IP. I am getting this error. @saarg

 

nginx: [emerg] PEM_read_bio_DHparams("/config/nginx/dhparams.pem") failed (SSL: error:0909006C:PEM routines:get_name:no start line:Expecting: DH PARAMETERS)

 

Not sure about the relevance of noip and email verification regarding your problem.

 

Show me your current port forward.

[Tucubanito07]

Just now, saarg said:

 

Not sure about the relevance of noip and email verification regarding your problem.

 

Show me your current port forward.

 

 

 

[saarg]

9 minutes ago, Tucubanito07 said:

 

 

 

You don't seem to understand how to port forward.

The external ports are 80 and 443. So change those. Your internal are correct for letsencrypt.

The error message is probably caused by your wrong portforward.

[Tucubanito07]

3 minutes ago, saarg said:

You don't seem to understand how to port forward.

The external ports are 80 and 443. So change those. Your internal are correct for letsencrypt.

The error message is probably caused by your wrong portforward.

I understand what you are saying. But even if i do the external 80 to internal 80 and the same for 443 it still does not work.

[Tucubanito07]

Here is all the screen shots. @saarg

 

 

[Tucubanito07]

[saarg]

2 minutes ago, Tucubanito07 said:

 

Would you be so kind and read what I say properly??

I told you to change the external ports only. Not the internal.

port 80 external goes to 180 internal.

port 443 external goes to 1443 internal.

 

I'm talking about the port forward in your router. Don't change anything on unraid.

[Tucubanito07]

6 minutes ago, saarg said:

 

Would you be so kind and read what I say properly??

I told you to change the external ports only. Not the internal.

port 80 external goes to 180 internal.

port 443 external goes to 1443 internal.

 

I'm talking about the port forward in your router. Don't change anything on unraid.

 

This is what i get when I port forwarding how you said. @saarg