nginx-wordpress-portainer

[Mr.Swiss0364]

Hello, So I am so lost right now, I am trying to get a wordpress website running for literally 2 days for my collage, but I cant just send them my public IP as they wont click on it. so I bought a domain on Namecheap and I'm hosting portainer on my proxmox server, I have wordpress running and I'm trying to use nginx via cloud flare to wordpress, I don't know. I'm so confused and I need to try to get it running by Monday. 

 

the error: so it works on my local machine, I have portainer running both wordpress and nginx. both work, and I have my domain connected to Cloudflare, and when I try to type in the domain I just times out on Cloudflare host.

 

This is the video I'm trying to follow: 

watch this incase I did not explain. I think the issue is the ports as I'm using an "EE" Router (From UK) and he is using an American one. I know every router is different. but my router is wildly different

His: 

 

"If the destination coming in is https or 443, take that turn it around this local IP "10.0.0.26" on this port "4043"

I'm using the same ports (not taken) and done everything exactly the same and it dose not work. if I'm missing info please ask and I can tell you. I'm stressing out as I don't want to fail because of this

[C2dan88]

54 minutes ago, Mr.Swiss0364 said:

I know every router is different. but my router is wildly different

I use BT/EE router. How I understand it you need to forward ssl ports 443 and 8443 to your portioner container ssl ports (40443 40080)

[Mr.Swiss0364]

1 minute ago, C2dan88 said:

I use BT/EE router. How I understand it you need to forward ports 443 and 8443 to your portioner container (40443 40080)

Would i do that in portainer, or in my BT / EE Router, like in the inboud or outbound

 

[Kisai]

48 minutes ago, Mr.Swiss0364 said:

Hello, So I am so lost right now, I am trying to get a wordpress website running for literally 2 days for my collage, but I cant just send them my public IP as they wont click on it. so I bought a domain on Namecheap and I'm hosting portainer on my proxmox server, I have wordpress running and I'm trying to use nginx via cloud flare to wordpress, I don't know. I'm so confused and I need to try to get it running by Monday. 

 

the error: so it works on my local machine, I have portainer running both wordpress and nginx. both work, and I have my domain connected to Cloudflare, and when I try to type in the domain I just times out on Cloudflare host.

 

This is the video I'm trying to follow: 

watch this incase I did not explain. I think the issue is the ports as I'm using an "EE" Router (From UK) and he is using an American one. I know every router is different. but my router is wildly different

His: 

 

"If the destination coming in is https or 443, take that turn it around this local IP "10.0.0.26" on this port "4043"

I'm using the same ports (not taken) and done everything exactly the same and it dose not work. if I'm missing info please ask and I can tell you. I'm stressing out as I don't want to fail because of this

 

What are you actually trying to do? (Aside from installing Wordpress, which is it's own mistake.)

 

If you just want a wordpress site, then you install wordpress on a server you have full control over. A "shared" account will lack the ability to modify the web server's configuration.

 

Once the wordpress works, THEN you start doing this other stuff. The impression I'm getting from this is you're trying to self-host wordpress inside your home on your own equipment, and use namecheap+cloudflare as a proxy. This is ... probably not the worst idea, but what is the goal here? Is this a collage project or a service for the collage? Cause if it's the latter, then this is the wrong way to go abou things.

 

Anyway, if this isn't working, it's because you need to make sure that the router opens port 80 and 443 to the internet and passes that to the machine on your network. That's all. If you want to access SFTP/SSH you also need to open the port you have SSH running on.

 

So you can just send 80 and 443 to 80 and 443 on your machine it's running on, but there will only be one machine that can do that. The reason you often see statements like this is because of an assumption of what you intend to do with opening those ports.

 

What you want, if only a single machine is involved is to have Cloudflare connect to your port 80 and 443 on your real IP address, and your router will send traffic sent at those ports to the destination machine, even at the same 80 and 443 ports. You only change those ports when you have an elaborate configuration (eg you have multiple websites running inside.)

 

 

[Mr.Swiss0364]

1 minute ago, Kisai said:

 

What are you actually trying to do? (Aside from installing Wordpress, which is it's own mistake.)

 

If you just want a wordpress site, then you install wordpress on a server you have full control over. A "shared" account will lack the ability to modify the web server's configuration.

 

Once the wordpress works, THEN you start doing this other stuff. The impression I'm getting from this is you're trying to self-host wordpress inside your home on your own equipment, and use namecheap+cloudflare as a proxy. This is ... probably not the worst idea, but what is the goal here? Is this a collage project or a service for the collage? Cause if it's the latter, then this is the wrong way to go abou things.

 

Anyway, if this isn't working, it's because you need to make sure that the router opens port 80 and 443 to the internet and passes that to the machine on your network. That's all. If you want to access SFTP/SSH you also need to open the port you have SSH running on.

 

So you can just send 80 and 443 to 80 and 443 on your machine it's running on, but there will only be one machine that can do that. The reason you often see statements like this is because of an assumption of what you intend to do with opening those ports.

 

What you want, if only a single machine is involved is to have Cloudflare connect to your port 80 and 443 on your real IP address, and your router will send traffic sent at those ports to the destination machine, even at the same 80 and 443 ports. You only change those ports when you have an elaborate configuration (eg you have multiple websites running inside.)

 

 

Its a project, the website is basically done, and all i have to do it get it hosted and working, then it goes down and deleted on Wednesday

[C2dan88]

4 minutes ago, Mr.Swiss0364 said:

or in my BT / EE Router, like in the inboud or outbound

Sorry mybad 8443 should be 80

You set these rules in the router. FIrst two boxes should be 443 80 last two should be 40443 40080

 

You can his forwarding rules @ 6:43 in video

[Mr.Swiss0364]

1 minute ago, C2dan88 said:

Sorry mybad 8443 should be 80

Router. FIrst two boxes should be 443 80 last two should be 40443 40080

You can his forwarding rules @ 6:43 in video

[C2dan88]

@Mr.Swiss0364

No, like this

 

All you are doing is forwarding 80 and 443 to your portioner.

[Mr.Swiss0364]

19 minutes ago, C2dan88 said:

@Mr.Swiss0364

No, like this

 

All you are doing is forwarding 80 and 443 to your portioner.

Ok, still not working. im going to get my sister from school, and will see when im back

 

[Mr.Swiss0364]

1 hour ago, C2dan88 said:

@Mr.Swiss0364

No, like this

 

All you are doing is forwarding 80 and 443 to your portioner.

Im hosting nginx on my portainer so it’s on the same IP, do I host it in a VM on proxmoz instead so it’s a different IP?

[Kilrah]

Your domain needs to point to your ip (proxying off if you're using cloudflare), ports 80/443 need to forward to your nginx reverse proxy's ip/port, the reverse proxy needs to forward requests for that domain to the ip/port of the WP server. Portainer must not get any port forwards or be externally accessible.

 

Once that works you can enable cloudflare proxying.

[Mr.Swiss0364]

2 hours ago, Kilrah said:

Your domain needs to point to your ip (proxying off if you're using cloudflare), ports 80/443 need to forward to your nginx reverse proxy's ip/port, the reverse proxy needs to forward requests for that domain to the ip/port of the WP server. Portainer must not get any port forwards or be externally accessible.

 

Once that works you can enable cloudflare proxying.

i only have the option for name servers i cant find the records. i have the Cloudflare name severs. im using name cheep witch i have used before

[Mr.Swiss0364]

2 hours ago, Kilrah said:

Your domain needs to point to your ip (proxying off if you're using cloudflare), ports 80/443 need to forward to your nginx reverse proxy's ip/port, the reverse proxy needs to forward requests for that domain to the ip/port of the WP server. Portainer must not get any port forwards or be externally accessible.

 

Once that works you can enable cloudflare proxying.

 

this is the domain in cloudflare, it has my public up in content. do i need more records?