Network issues - is my FBx configuration correct?

I have a complex and chaotic issue with accessing my FBx from external. It is different to the one discussed here before and I realized it after changing the scheme with my provider to higher speed and lower cost. Probably the cause is somewhere at my provider and a wrong configuration of my router, not the FBx. All my computers are connecting via WLAN to the router.
But to start with, I want to make sure the FBx network connection is correct especially the assignment of internal/external for the Firewall.
My FBx is a Raspberry 4B, connected via LAN to the router which connects to the internet.
In my FBx the network connections are set by default to :

Aktiv 	        Wired connection 1 	Ethernet (eth0, primary, intern)
Aktiv 	        lo 	                loopback 	
Inaktiv 	FreedomBox WAN 	        Ethernet (eth0, extern)

In this configuration everything works fine (except the network issues from external) except Privoxy. To have this working I have to activate “FreedomBox WAN”, which is deactivated after every restart. Thus I am wondering if this configuration with or without acive WAN is correct?

Do you have a domain and services connected to that domain?

Some thoughts: I guess, that your config with a WAN and a LAN is not correct. You need to have either a LAN or a WAN connection configured, as much as I know and have learned.

You need a LAN connection from your router (with WLAN) to your FBX.
Or if you need access from outside to your FBX, then you need to configure your router with domain resolution, so he knows, where to route the incoming traffic to.

Another way is to open your router to forward all WAN traffic to your FBX. In this case you need to find a way, how access your FBX from your LAN.

Yes, I do have a domain. DynDNS is configured in the FBx and I think it’s set up correctly. Nevertheless, I will check all these steps again, to be sure.
Maybe the issues have to do with IPv6 as well.

So active LAN is correct if the path goes from the router to the FBx, I understand. Keeping WAN inactive is thus the consequence. That makes sense as this is the default configuration on my FBx.
However, why does Privoxy not work in this configuration?