Self-Signed from NginxProxyManager to Zeroxy, Problem with Certificate

[Chiller2019]

Hey,

I have a question.
With NginxProxyManager you can include a wildcard certificate and use it for each host. For this I have packed each container including NginxProxyManager (or now Zeroxy) in its own network.

I didn't open any ports at the time because Nginx didn't need them.

With Zeroxy, I integrated my wildcard certificate as TLS and as fallback TLS. However, it cannot open the fixed IP of the container even though the IP and port are specified.

Does anyone here have experience with self-signed and Zeroxy to explain this to me quickly?

Kind regards

//When I try to ping the server via Network Tools -> Traceroute/Ping, TCP connection refused is returned although they are in the same network

[tobychui]

Hey @Chiller2019 ,

Can you show a screenshot of your proxy rules and setup here? It seems like a networking issue to me than a bug in Zoraxy.

[Chiller2019]

IP-Scanner:

Old Config of NGinxProxyManager (Custom is the Wildcard-Certificate because its self-signed and not with ACME, dont use ACME):

Zoraxy HTTP-Proxy:

TLS:

Portainer-Network (all with fixed-ips):

Portainer-Container-PDF:

Portainer-Container-Zoraxy:

Enviroments of Zoraxy:

Zoraxy-Global settings:

[tobychui]

The settings all seems ok to me, have you tried running Zoraxy without docker (e.g. run it on your PC locally, with the same setup) and see if it works?

And your PDF container have no published port in your screenshot, you sure that is correct?

[Chiller2019]

That's what I thought.
I haven't tried that yet either, but it's also more difficult because of the effort involved. These are split into a separate network and can only be accessed via the proxy, you shouldn't be able to access them easily via IP or port but only via the preset domain.

I would be interested to know whether a proxy rule really uses this characteristic. Although it should still be able to access it via docker.sock.

And yes, the container does not need a public port. NxingProxyManager did not need that. Not sure why either.
But I'll try to open the port, it only works as a user of the “StaticNetwork” anyway

[Chiller2019]

Ok, the error is fixed. Zoraxy had to be restarted.
The question is whether I have to restart Zoraxy every time I start a new service or not.

Port does not have to be set, it worked the same way for me

[Chiller2019]

@tobychui Thx for your quick answer!