two pyro5 daemons with multiplex servers

In essence I need a message bus daemon and separate mover of python objects daemon on one server. Ideally, I need message bus on localhost to serialize input. on the other side I need ssl daemon that will get that input and expose it for move over the network.
Problem is that I am unable to start ssl daemon as it is complaining that I am using same server (socket issue). i understood that multiplex servers are capable of joining into master daemon loop, but aside from combaining ns and broadcast server into single daemon I can't do this on my own daemons above.
Is this possible and if it is can someone explain to me how to do this?

This is not true? I ran many deamons on my single IP system. There are even a bunch of examples included in the repo that show how to do this including a dispatcher even. What exactly are you trying to do? @catchthemonster

edit: oh I see you opened a separate issue about this. Please answer there, to avoid necromancing this issue here

I thought so too, and i got it finally to work but i still have some residual issues:

ok so I want to achieve this:

app1 message to localhost pyro5 daemon server (no ns and broadcast) messagebus: memory (your code Irmen)

other daemon also part of the same python app that contains messagebus is 2-way ssl daemon on the local net (cloud) that will get a signal from the serialized message (disk) and expose this to remote object pull of payload

So I have one app two daemons and master daemon that combines both event loops (again from your event loop code) both daemons are working now with protocols answering on localhost and actual lan ip

I can publish message via your publich client (separate script) to first daemon (messagebus). For what ever reason subscribe script will not pick it up. I am not sure why as i got it to work in your example version just fine.

In essence, I just wrapped in separate daemon classes ssl 2-way on public IP and on localhost message bus. then in wrapper for Pyro5 I used master daemon to combine event loops.

The other ancillary app is also on the server and I can easily integrate publisher code to that app to send message to Pyro that some payload (python object) is ready to be picked up and moved over the wire with another pyro app that I have outside of local network.

I hope this helps and thank you for confirming that multiple daemons work with multiplex-servers or threads...

I am not sure on subscribe thing but I guess some debugging of code and then changing some will do it ... it seems that my wrapping has something to do with messagebus but I am not sure what... i start my app then I do subscriber that perfectly connects to daemon and gets to the topic. after that I publish message fine and message bus does acknowledge that but subscriber will not pick it up ...