• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

TFS 1.X+ Error starting http server

Mjmackan

Mapper ~ Writer
Joined
Jul 18, 2009
Messages
1,444
Solutions
16
Reaction score
180
Location
Sweden
Using the latest sources, after successfully compiling and running the server i get this print shown in console below and then the console exits.

-Mysql is set up.
-Website is set up.
-Ports are open(even tried to turn off firewall)

1751738748776.webp
 
Solution
MyAAC does not work with TFS 1.6+ (EDIT: TFS 1.6 was released 5 days after commit that breaks login with MyAAC, so it's not only broken on 1.7, also on 1.6). No AAC works with newest TFS, since they implemented 'own' sessions key algorithm (12+ client feature processed by login.php of MyAAC), that works only with 'build in HTTP' login server. One that makes your server crash on start, if you don't disable it with httpWorkers = 0.

PR that broke compatibility with MyAAC has 12+ months:
It was reported as a problem 5 days after this...
i get this print shown in console below and then the console exits.
Run console first (hold Shift and press right mouse button in empty space in TFS folder to show extra 'terminal' [bash/cmd/powershell] options) and then run TFS by command ex. .\theforgottenserver-x64.exe (PowerShell) or ./theforgottenserver-x64.exe (Git Bash).
Then it won't close terminal on error and you will see messages.
 
Run console first (hold Shift and press right mouse button in empty space in TFS folder to show extra 'terminal' [bash/cmd/powershell] options) and then run TFS by command ex. .\theforgottenserver-x64.exe (PowerShell) or ./theforgottenserver-x64.exe (Git Bash).
Then it won't close terminal on error and you will see messages.
>> Starting HTTP server on 90.227.183.136:8080 with 1 threads.
PS C:\forgottenserver-1.6>

So many new things, what does this even do? Checks my ports and such? When i set the 'httpWorkers' to 0 it finally came to life but then i got a session error in mysql, not sure if thats cuz i run myaac and mehahclient which really not support 13.10 either of em.

Think I need to take a break into the sauna, I just wanted to mess with all the new features and thingys of TFS not spend hours on compiling and hosting hehe.
 
MyAAC does not work with TFS 1.6+ (EDIT: TFS 1.6 was released 5 days after commit that breaks login with MyAAC, so it's not only broken on 1.7, also on 1.6). No AAC works with newest TFS, since they implemented 'own' sessions key algorithm (12+ client feature processed by login.php of MyAAC), that works only with 'build in HTTP' login server. One that makes your server crash on start, if you don't disable it with httpWorkers = 0.

PR that broke compatibility with MyAAC has 12+ months:
It was reported as a problem 5 days after this PR:
report was closed with 'go fix your acc. maker', but nobody worked on MyAAC update, as nobody hosts OTS based on TFS 1.6+ engine.

I tried to run TFS master around 2 months ago on Windows and I gave up after 1 hour of configuring all that crap.
In last weeks I made multiple PRs:
some of them are merge, some are not.

With all these changes I can compile TFS on Windows and run it with build-in HTTP server, which makes it possible to login, if you set URL to login to http://127.0.0.1:8080/ in client (using ex. OTS IP Changer for Tibia 12+ (https://ots.me/ots-ip-changer-12/) )
It's also possible to run TFS in Docker on Windows with 1 command docker compose up, but this PR is still waiting for approval.
Starting HTTP server on 90.227.183.136:8080 with 1 threads.
I would try to set server IP to 127.0.0.1 in config.lua and start it with HTTP workers enabled. Maybe it's Windows problem of binding to IP that is not assigned to any network interface (you probably use DMZ / port forwarding on router).
If changing to 127.0.0.1 fixed problem with starting server with HTTP enabled, this is PR that fixes it:
It makes TFS listens on all possible IPs, but returns ip from config.lua as server IP on 'characters list',
but it's not merge yet. You must apply these changes yourself.
 
Last edited:
Solution
MyAAC does not work with TFS 1.6+ (EDIT: TFS 1.6 was released 5 days after commit that breaks login with MyAAC, so it's not only broken on 1.7, also on 1.6). No AAC works with newest TFS, since they implemented 'own' sessions key algorithm (12+ client feature processed by login.php of MyAAC), that works only with 'build in HTTP' login server. One that makes your server crash on start, if you don't disable it with httpWorkers = 0.

PR that broke compatibility with MyAAC has 12+ months:
It was reported as a problem 5 days after this PR:
report was closed with 'go fix your acc. maker', but nobody worked on MyAAC update, as nobody hosts OTS based on TFS 1.6+ engine.

I tried to run TFS master around 2 months ago on Windows and I gave up after 1 hour of configuring all that crap.
In last weeks I made multiple PRs:
some of them are merge, some are not.

With all these changes I can compile TFS on Windows and run it with build-in HTTP server, which makes it possible to login, if you set URL to login to http://127.0.0.1:8080/ in client (using ex. OTS IP Changer for Tibia 12+ (https://ots.me/ots-ip-changer-12/) )
It's also possible to run TFS in Docker on Windows with 1 command docker compose up, but this PR is still waiting for approval.

I would try to set server IP to 127.0.0.1 in config.lua and start it with HTTP workers enabled. Maybe it's Windows problem of binding to IP that is not assigned to any network interface (you probably use DMZ / port forwarding on router).
If changing to 127.0.0.1 fixed problem with starting server with HTTP enabled, this is PR that fixes it:
It makes TFS listens on all possible IPs, but returns ip from config.lua as server IP on 'characters list',
but it's not merge yet. You must apply these changes yourself.
Jesus Gesior, ur THE man.
Thanks for explaining all this to me instead of forcing me to look up all this info, it really shortened the process.
I'll check out your PRs, thank you again.

I tried with 127.0.0.1 firstly, since back in the days i had exactly that problem, but im pretty sure i took care of it, I dont use DMZ as I've been lectured through that the harsh way.
 
Back
Top