Wordpress app installed on worker node, traffic doesn't seem to route between the leader and worker

[BigSteve (Steve Spanjers)]

NethServer Version: 8
Module: traefik or wordpress

As the title says, I can’t seem to get traffic routing between the leader node and worker node for the wordpress app. I am trying currently with no LE cert to see if I can get it working. DNS is resolving properly, and pointing to the leader node. The leader node has the automatic route generated showing that wordpress is on node 2 (worker node), but the web page gives a 404 not found error. I tried creating a manual route to the WG network on the worker node, but that resulted in too many redirects.

Any ideas what I might be missing to get this working?

Thanks!

[mrmarkuz (Markus Neuberger)]

There’s no automatic routing from leader to worker node, you need to set the route manually, see for example Apps running on second node should be accessible from Leader - #7 by mrmarkuz how to do it.

[stephdl (Stéphane de Labrusse)]

@BigSteve

DNS is resolving properly, and pointing to the leader node. The leader node has the automatic route generated showing that wordpress is on node 2 (worker node), but the web page gives a 404 not found error.

if wordpress is on node 2 then the A field dns must give back the ip of the node 2

[BigSteve (Steve Spanjers)]

Is it best practice to point to node 2, or point to the leader node with a route to node 2 as suggested above?

[BigSteve (Steve Spanjers)]

@mrmarkuz

There’s no automatic routing from leader to worker node, you need to set the route manually, see for example Apps running on second node should be accessible from Leader - #7 by mrmarkuz how to do it.

This worked! I had a rule created that didn’t solve the issue initially. I was on the right track, but I didn’t point to the https:// version of the VPN IP, and didn’t have skip certficate verification checked.

Thanks so much for the quick reply!

[mrmarkuz (Markus Neuberger)]

@BigSteve

Is it best practice to point to node 2

It’s intended to setup the DNS to point to the node on which an app is installed.

But using HTTP routes, it’s possible to route to any node, even to internal ones.

[stephdl (Stéphane de Labrusse)]

@BigSteve

Is it best practice to point to node 2, or point to the leader node with a route to node 2 as suggested above

create a dns entry where the app is running is the simple solution, a route is the complicated one like you discovered

[BigSteve (Steve Spanjers)]

One more quick (related) question, if I run mulitple Wordpress apps for multiple sites, I would need to use http routes? Or could both sites point to the same worker node via DNS?

[mrmarkuz (Markus Neuberger)]

In the NS8 Wordpress instance app settings you setup a FQDN for the instance over which it is reachable.

So both is possible, both sites FQDNs can point to the same worker node via DNS or you could setup http routes on the leader for both sites via the FQDN as host.