Just FYI, X-haven creating the IP using your local address should not matter, as long as you tell the router to port forward whatever external port you are using to the correct one in X-Haven.

That said, I did notice that changing ports in X-haven on the latest download as of 2 days ago did not seem to really save the ports, so once I configured my port forwards using the default 4567 to my hosting machine, others connected just fine to my public IP.

Port settings are only saved when you start the server (this is regular assistant behavior). I could also have introduced a bug making even that broken ... will check.

I had not used it so was not aware, but I'll try changing it tomorrow.

Thanks for the comments. Turns out I'm a big dummy and was looking at the wrong IP. I didn't notice that the first IP listed is local, while the other is public. Have been using it without difficulty since this realization.

OK. The other day I tested narration with someone, it was them hearing it over Discord instead of in game. Just spent a bit of time working on getting TTS sharing to work since I am the only one that purchased the narration assets.

I am using the current Workshop version. When I start X-haven, start the server (with web server enabled), I have verified my firewall is allowing port 8080 to my host machine. Doing a http://my-static-external-ip:8080/state shows the JSON info for all my friends, so firewall is forwarding correctly.

When loading the mod, it by default shows localhost and when you enable the integration it connects just fine. If I make sure the Narration is NOT going to the assistant, but TTS, obviously like that nobody hears anything. If I then disable the assistant integration checkbox, change the localhost line to my external IP, hit enter, and re-enable assistant, I get the following:

https://imgur.com/a/C3gsdbO

If I disable the integration, change it back to localhost, or 127.0.0.1, or anything else and turn it back on, the same error persists. I have to go and load a new workshop mod game for it to go away. I then took the fresh mod file, and went into it and manually changed the localhost instances to my static external IP. I then loaded the mod and it worked! for like 15 minutes, before it changed itself back to 127.0.0.1 and stopped working again.

By this point I had been messing with it to get it working fcor a couple hours so we gave up for the night.

If me running your dev save off github can help gather info, or you would like me to host a session to test, let me know, but I have no clue whats happening. Even if you can tell me what lines to correctly hard code my IP into it would be appreciated.

Thanks!

The issue is pressing "enter" after you type your IP. I'll add code to deal with that. "Enter" simply adds a new line to your address, which isn't valid anymore after that...

I've pushed a version to github, that should now ignore "enter" in address and port.

Aaahhh. OK, thanks sir. Never figured that would be it.