Im starting to think that my port 80 is blocked by my ISP. I'm not sure how bad this is, as i can still reach nextcloud externally on 443.

I tried all the NAT reflection options with rebooting after each change, but still no succes..

Im starting to think that my port 80 is blocked by my ISP. I'm not sure how bad this is, as i can still reach nextcloud externally on 443.
I tried all the NAT reflection options with rebooting after each change, but still no succes..

I think that makes more sense. I know ISP can do it as long you use their router.

But if you say nextcloud works using port 443. Maybe force let's encrypt to redirect traffic to 443 only?

I did it by going to the appdata/letsencrypt/nginx/site-confs/

And edit the default

The setting is already there is just enabling it.

I'm just guessing right now because is really specific

Sent from my Pixel 2 XL using Tapatalk

Is there anything special I need to do in order to send email from the nginx using php's mail() function?

Hey Guys,

 

I need some help. I am getting this on the logs for letsencrypt. Two errors. I have followed Spaceinvader and Techcoreduo and i cant get it to work outside my network.

 

nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)

 

nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:

 

 

 

Edited May 28, 20197 yr by Tucubanito07

Hey Guys,
 
I need some help. I am getting this on the logs for letsencrypt. Two errors. I have followed Spaceinvader and Techcoreduo and i cant get it to work outside my network.
 
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
 
nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:
 
 
 

Look back a couple pages; it's been covered very recently [emoji854]

Sent from my SM-G975U using Tapatalk

Look back a couple pages; it's been covered very recently [emoji854]

Sent from my SM-G975U using Tapatalk

Also, shouldn't you be using TCP instead of UDP [emoji848]?

Sent from my Pixel 2 XL using Tapatalk

7 hours ago, gacpac said:

Also, shouldn't you be using TCP instead of UDP ?

Sent from my Pixel 2 XL using Tapatalk
 

Yeah he should use tcp for 80 and 443 and is the reason for the issues.

@Tucubanito07

The errors you have is harmless as said on the last couple of pages. Change your port forwards to use tcp as Tupac says above, and you should be closer to get it working.

 

1 hour ago, saarg said:

8 hours ago, gacpac said:

 

1 hour ago, saarg said:

as Tupac says above

ROTFL. Autocorrect?

2 hours ago, jonathanm said:

 

ROTFL. Autocorrect?

This time it was absolutely not autocorrect 😁

2 minutes ago, sgt_spike said:

Can some tell me what these errors mean?

 

Just read the last few posts man, come on now

1 hour ago, aptalca said:

Just read the last few posts man, come on now

Duh!!! My bad....I know reading is fundamental! 

 

Also, I am trying to setup the mail mod in nginx.  In the nginx.conf, I uncommented the mail section and copied/edited the php script from the wiki page.  I edited the script to use my IP of my unraid.  in the conf file the auth_http is set to the location of the script file.

How can I tell if it's working?

Edited May 29, 20197 yr by sgt_spike
adding to

5 hours ago, saarg said:

Yeah he should use tcp for 80 and 443 and is the reason for the issues.

@Tucubanito07

The errors you have is harmless as said on the last couple of pages. Change your port forwards to use tcp as Tupac says above, and you should be closer to get it working.

 

So change my router to port forward to 80 and 443 ?

So change my router to port forward to 80 and 443 ?

Probably be a good place to start. May have to reference back through SpaceInvaders videos, he shows how to set it up and you can figure our where yours is broke.

Sent from my SM-G975U using Tapatalk

2 minutes ago, blaine07 said:

Probably be a good place to start. May have to reference back through SpaceInvaders videos, he shows how to set it up and you can figure our where yours is broke.

Sent from my SM-G975U using Tapatalk
 

I followed his instructions to the teeth and it did not work. I am going to delete everything and restart from fresh again and see if that helps. But I have already done it with space invader. 

I followed his instructions to the teeth and it did not work. I am going to delete everything and restart from fresh again and see if that helps. But I have already done it with space invader. 

That's what guide I used with success. Pfsense is my router FWIW.

Sent from my SM-G975U using Tapatalk

1 minute ago, blaine07 said:

That's what guide I used with success. Pfsense is my router FWIW.

Sent from my SM-G975U using Tapatalk
 

I am using the router from my isp provider.  It has to do with the port forwarding ports. 

I am using the router from my isp provider.  It has to do with the port forwarding ports. 

I'm not sure how but might be worth looking into if your provider blocks 80; it isn't unheard of

Sent from my SM-G975U using Tapatalk

5 minutes ago, blaine07 said:

I'm not sure how but might be worth looking into if your provider blocks 80; it isn't unheard of

Sent from my SM-G975U using Tapatalk
 

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

 

 

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

I think that's forwarding to your unraid server directly?

Sent from my Pixel 2 XL using Tapatalk

1 minute ago, gacpac said:

I think that's forwarding to your unraid server directly?

Sent from my Pixel 2 XL using Tapatalk
 

I believe that is what it is. So i change it to this and this is what i get now.

It also seems like No-IP is not refreshing on their website for the DNS. Lokk at the screen shot i grabbed from no-IP.

 

I believe that is what it is. So i change it to this and this is what i get now.

Cool. So we are im busines now. Look at the link you have.

It's https but then going to port 80. Is wrong



Sent from my Pixel 2 XL using Tapatalk

4 minutes ago, gacpac said:

Cool. So we are im busines now. Look at the link you have.

It's https but then going to port 80. Is wrong



Sent from my Pixel 2 XL using Tapatalk
 

Where do I need to look or change for this specific error? Thank you guys for the help. Really appreciated a lot. 

12 minutes ago, Tucubanito07 said:

Where do I need to look or change for this specific error? Thank you guys for the help. Really appreciated a lot. 

Honestly, 

 

Check both config files. Because it's redirecting somewhere else. If I go to the website it redirects me to https://nextcloud-eleanor.ddns.net:80/login

 

But If I type your public IP address in the browser. (Which I'm not going to type for security)

 

I get this

 

I think you gotta fix some security issues in your router, my friend.

 

That should be hitting the nginx webserver built in let's encrypt not straight to your nextcloud. 

 

Please someone correct me if I'm wrong. I might be mistaken

31 minutes ago, gacpac said:

Honestly, 

 

Check both config files. Because it's redirecting somewhere else. If I go to the website it redirects me to https://nextcloud-eleanor.ddns.net:80/login

 

But If I type your public IP address in the browser. (Which I'm not going to type for security)

 

I get this

 

I think you gotta fix some security issues in your router, my friend.

 

That should be hitting the nginx webserver built in let's encrypt not straight to your nextcloud. 

 

Please someone correct me if I'm wrong. I might be mistaken

This is how it looks.