cant makes the server public

Newbie Spellweaver
Joined
Sep 25, 2025
Messages
10
Reaction score
2
hi great people,
first of all, I'm learning alot from that forum, that's amazing.

Im currently running the florist files v18, and I do managed to run the server Locally.
now I'm trying to go live..
after going through the guide of making it Public, i had to make few changes on the source code:
1760026333494 - cant makes the server public - RaGEZONE Forums

i used my wan-ip, and changed the local_TEST to False.
next, i compile the code, and edit the ini's:
accountserver.ini:
1760026522149 - cant makes the server public - RaGEZONE Forums


and loginserver.ini :
1760026565544 - cant makes the server public - RaGEZONE Forums


Next, opened the ports 15400,5400, 23000,28000 on my firewall, and in portforward the ports In my router as well..
now when I'm trying to run the neuz its not even opening..
did I miss something? some1 have any pictures of the right configuration of the ports inside the files ? or have any idea what should I check to make it work?

Best regards <3
 
Server Information
Florist release v18
Make sure your data.res is in your client and that nothing is missing from it. But usually, those files are already configured, if I remember correctly. I can check add me on Discord: zacksfff
And leave my-wan-ip as 127.0.0.1 for now if you’re running locally no need to change it.
 
Upvote 0
Make sure your data.res is in your client and that nothing is missing from it. But usually, those files are already configured, if I remember correctly. I can check add me on Discord: zacksfff
And leave my-wan-ip as 127.0.0.1 for now if you’re running locally no need to change it.
i already added you on discord, and massage you, no reply :>
locally works very well, i want to try go live with my friends.
i do have the data.res on my client..
 
Upvote 0
I reread your message and replied to you on Discord.
You just need to put your VPS IP address in the .ini files.
In the account.exe, allow external connections.
In the CustomCommon file, set it to FALSE and enter your VPS IP address.
I don’t understand why you put “WAN IP.”
 
Upvote 0
I reread your message and replied to you on Discord.
You just need to put your VPS IP address in the .ini files.
In the account.exe, allow external connections.
In the CustomCommon file, set it to FALSE and enter your VPS IP address.
I don’t understand why you put “WAN IP.”
thanks for replying
I'm not using VPS I'm actually running it on my pc, I did allowed external connections on the account.exe
and set as the picture to FALSE
after all that, the neuz isn't start

if I'm running it with my pc, which ip I should use ?
and what else can be the cause that my neuz doesn't work?
 
Upvote 0
hi great people,
first of all, I'm learning alot from that forum, that's amazing.

Im currently running the florist files v18, and I do managed to run the server Locally.
now I'm trying to go live..
after going through the guide of making it Public, i had to make few changes on the source code:
View attachment 289994
i used my wan-ip, and changed the local_TEST to False.
next, i compile the code, and edit the ini's:
accountserver.ini:
View attachment 289995

and loginserver.ini :
View attachment 289996

Next, opened the ports 15400,5400, 23000,28000 on my firewall, and in portforward the ports In my router as well..
now when I'm trying to run the neuz its not even opening..
did I miss something? some1 have any pictures of the right configuration of the ports inside the files ? or have any idea what should I check to make it work?

Best regards <3
Try to remove "my-wan-IP" and change it to your IP address. Maybe it will fix your problem.
 
Upvote 0
If the neuz isnt opening you most likely have a boothash defined. As anything else you might have missed would def throw some errors. If it is, feel free to post said errors.

idk why people are talking about your IP address, it is not your issue. The IP isnt going to stop neuz from opening.
 
Upvote 0
wow so much knowledge here
If the neuz isnt opening you most likely have a boothash defined. As anything else you might have missed would def throw some errors. If it is, feel free to post said errors.

idk why people are talking about your IP address, it is not your issue. The IP isnt going to stop neuz from opening.
maybe if hes using vps, considering checking the ports if it's open?
 
Upvote 0
So you are saying the ports, even if they are not open, will cause NEUZ to not open?

That was his question. " why when i made the server public will neuz not open. "

It is because a lot of files have disabled the boot hash from the testing environment and upon reenabling it is now needed again. Without it, it will not open. Datasubs would throw massive errors, Ports being closed will show connection cant be made upon logging in. and since its working fine locally, one could only assume his datasubs are indeed there. :rolleyes:
 
Upvote 0
So you are saying the ports, even if they are not open, will cause NEUZ to not open?

That was his question. " why when i made the server public will neuz not open. "

It is because a lot of files have disabled the boot hash from the testing environment and upon reenabling it is now needed again. Without it, it will not open. Datasubs would throw massive errors, Ports being closed will show connection cant be made upon logging in. and since its working fine locally, one could only assume his datasubs are indeed there. :rolleyes:
awesome, thanks for that
 
Upvote 0
Back