i'm experiencing a minor issue. I refer to the way that the APIs check if the server is online or not. in most scenarios, if you install the server in a Windows VM that has directly the public IP available without NAT or Router Firewall it works. My scenario is different as i don't expose directly windows or linux servers on the internet.
To let you understand:
Internet -> Firewall ->VM
Public IP NAT
so my internal network differs from the public IP declared into the MysqlDatabase.
this cause the APIs to try exit the firewall and be back on the firewall wan port exposed, and the firewall will not allow such thing, on the other hand in the DB i must put the PUBLIC IP to let the client connect. Is there a way to include the IP To Check inside the .env config file to let handle most complex scenarios?
Thanks in Advance.
17-06-22
Lord Moon
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by hsdn
Yes.
Also you need to enable option LOG_IP_ADDRESSES_FORWARDED_FOR in your .env if you want to log the real client IP addresses.
I did that and now i get the error 274 (11): ini error
17-06-22
hsdn
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by Lord Moon
I did that and now i get the error 274 (11): ini error
Check api log. You need use https:// instead of http:// for launcherMain and http:// for launcher_mask (https not work on this).
18-06-22
vileninja
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Is it possible to add the ability to use more than just one language? Maybe add a selector that can be enabled and if enabled it checks if tw ru kor etc DC files and then launches using those languages?
18-06-22
hexaDoc
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by vileninja
Is it possible to add the ability to use more than just one language? Maybe add a selector that can be enabled and if enabled it checks if tw ru kor etc DC files and then launches using those languages?
if HSDN launcher uses the vanilla launcher, its fairly easy, how I did on my side was just to create a function that will modify the global variable containing the language string and modifies it through buttons that calls this function, by exemple in the launcher's HTML:
<button onclick="change_language('EUR');return false">EUR</button>
<button onclick="change_language('FRA');return false">FRA</button>
<button onclick="change_language('GER');return false">GER</button>
<button onclick="change_language('RUS');return false">RUS</button>
And in the JS functions_launcher.js:
function change_language(lan) {
language = lan;
}
It can be made a better way ofc.
18-06-22
hsdn
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by vileninja
Is it possible to add the ability to use more than just one language? Maybe add a selector that can be enabled and if enabled it checks if tw ru kor etc DC files and then launches using those languages?
In future versions, perhaps this will be added to the main launcher window.
21-06-22
lordomega87
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
@hsdn
as far the implementation of recaptcha is quite Easy,
create the google account and declare the fqdn hostname, using recapcha v3, enabling all the 3 options in the google page, using correctly the .env file to enable that feature, setting the 2 keys correctly
to me that function is still not working :D
Quite Weird as i triple checked all
21-06-22
argeus99
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by lordomega87
@hsdn
as far the implementation of recaptcha is quite Easy,
create the google account and declare the fqdn hostname, using recapcha v3, enabling all the 3 options in the google page, using correctly the .env file to enable that feature, setting the 2 keys correctly
to me that function is still not working :D
Quite Weird as i triple checked all
I had the same issue some days ago, changed to v3 and disabled this option in the recaptcha admin panel "Verify Origin" and worked at first try
21-06-22
lordomega87
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
@hsdn
done. made it from scratch. but the windows server machine name is not FQDN. should i change it to the FQDN name where it responds at through the frontend ha proxy?
because the LauncherSignupForm web page will not load it as before :D
-- update ---
if you need, i can post here the debug messages of the APIs, removing the Priv Keys
21-06-22
hsdn
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
I have good news for everyone!
In the near future, the full implementation of TERA Shop with promocode functions and Admin Panel for Tera API (management of the shop, accounts, bans, server list, maintenance, etc) will be published. The TERA Shop is part of the Tera API.
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Wow nice!
I have built my own tera shop but I am running into some javascript not loading errors when launching via the game. If anyone has a clue where can I look for the answer, please do tell :D
21-06-22
hsdn
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by smashking
I have built my own tera shop but I am running into some javascript not loading errors when launching via the game. If anyone has a clue where can I look for the answer, please do tell :D
TERA Shop uses Internet Explorer engine, you need to use legacy javascript. For the functions of _tera_client_proxy_ class to work, you also need to initialize the game browser engine. Getting a shop Token is done via arb_gw, endpoint /authApi/RequestAuthkey (but this hasn't been done yet in the latest published version of tera api).
21-06-22
S37uP!Update
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by hsdn
I have good news for everyone!
In the near future, the full implementation of TERA Shop with promocode functions and Admin Panel for Tera API (management of the shop, accounts, bans, server list, maintenance, etc) will be published. The TERA Shop is part of the Tera API.
Is there a posibility that you implement the Admin WebApp into the api since the code is already build, i guess the API can handle it since there's http/s connection to API used for launcher, idk just an idea.
Also very nice the TERA SHOP will be implemented, also the PROMO CODE is a nice thing too, keep the good work comming.
Please add the admin webapp as part of api if it's possible.
21-06-22
TieLay
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by hsdn
TERA Shop uses Internet Explorer engine, you need to use legacy javascript. For the functions of _tera_client_proxy_ class to work, you also need to initialize the game browser engine. Getting a shop Token is done via arb_gw, endpoint /authApi/RequestAuthkey (but this hasn't been done yet in the latest published version of tera api).
me sad but M$ stop using IE from 15 jun 2022
21-06-22
vileninja
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by TieLay
me sad but M$ stop using IE from 15 jun 2022
IE is still apart of windows. It is usually apart of Microsoft edge now. You will never be with IE
22-06-22
hsdn
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by vileninja
IE is still apart of windows. It is usually apart of Microsoft edge now. You will never be with IE
Tera uses the built-in browser library based on IE. Probably stopping support IE in Windows should not cause a problem.
UPD: Screen of shop promocodes implementation in api:
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Any chance there is a possibility you plan to integrate paypal api into your api?
25-06-22
TieLay
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by smashking
Any chance there is a possibility you plan to integrate paypal api into your api?
it's joke, rely... rely?
25-06-22
S37uP!Update
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by smashking
Any chance there is a possibility you plan to integrate paypal api into your api?
:junglejane::junglejane::junglejane:
25-06-22
smashking
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Asked a simple question, if the answer is no, then no, but where does the need of hate commenting comes from :)
25-06-22
dziobus
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by smashking
Asked a simple question, if the answer is no, then no, but where does the need of hate commenting comes from :)
Because asking for that specifically directly implies you are looking to make profit off of other peoples work asking for such a thing. Everything done here is for your own use, if you intend to open up a public private server because that is the only reason why you would need a paypal integration, you should not do so without an approval from those who created and setup all the tools and fixes here.
That is a simple grasp on why the comments.
25-06-22
smashking
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Thanks for having patience and manners for this answer :) Well yes you are correct in regards to the direct implication just as you are correct I shouldn't do it without creator's permission, but that doesn't mean that I am simply another freeloader kid who just takes and gives nothing back (not saying that you are saying that:) ) I can continue to "explaining and excusing" myself for the question I asked hsdn but I see no point to wasting time on people who drop random comments like this is a Facebook post from a cringe influencer. People need to grow out of medieval mindset and let the creator talk first, where following it is his and only his decision whether do it, share it, sell it or whatever and lastly answer my question.
P.S. I hope I didn't come accross as rude, I do appreciate your answer :)
25-06-22
hsdn
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by smashking
Any chance there is a possibility you plan to integrate paypal api into your api?
This is a part of the game website, it has not been implemented yet.
- - - Updated - - -
Quote:
Originally Posted by dziobus
Because asking for that specifically directly implies you are looking to make profit off of other peoples work asking for such a thing. Everything done here is for your own use, if you intend to open up a public private server because that is the only reason why you would need a paypal integration, you should not do so without an approval from those who created and setup all the tools and fixes here.
That is a simple grasp on why the comments.
I will bring a little clarity to your argument.
Since all of my products are distributed under the MIT license, you can use them commercially, resell or make money.
I do not forbid it to you :):
25-06-22
smashking
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Thanks once again hsdn :)
25-06-22
dziobus
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by hsdn
This is a part of the game website, it has not been implemented yet.
I will bring a little clarity to your argument.
Since all of my products are distributed under the MIT license, you can use them commercially, resell or make money.
I do not forbid it to you :):
Good to know. But still :P
You cant imagine how we all appreciate what you are doing here, so thank you for that :)
26-06-22
Luciole
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by smashking
Any chance there is a possibility you plan to integrate paypal api into your api?
Another thing that i want to add following the few posts send after this one, is if you're not able to add paypal API to existing code by yourself you should not try to open a server for commercial use.
I'm not saying that in a bad way, just as an advice
26-06-22
smashking
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Totally agree with you :)
26-06-22
vileninja
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
So when I try to use the updater Fi get a error saying it can't find 1-1.cab but it's there. In the console it's looking for localhost/public/patch/1/1-1.cab how do I tell it not to look for the /1 bc that duplicates the patch size
- - - Updated - - -
Now I'm getting can't access file launcher.exe a buddy is getting can't access server.db how do we fix this?
- - - Updated - - -
had to make a copy and run the copy to get past it. How do i stop from having to do that in the future?
01-07-22
vileninja
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
I have elite status id set to 0 in .env but it still gives vip pc cafe and founder. I wanna edit those and change what it gives but I cant find it.
03-07-22
hsdn
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by vileninja
I have elite status id set to 0 in .env but it still gives vip pc cafe and founder. I wanna edit those and change what it gives but I cant find it.
Just remove this lines from file or change ids.
03-07-22
chuchocr
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Hi all!
I am new here. I am trying to get my first private server. But the project tera-client-packer is taking a lot of time.
Has anyone encounter this problem?
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by hsdn
Just remove this lines from file or change ids.
Which files are you talking about?
- - - Updated - - -
Quote:
Originally Posted by chuchocr
Hi all!
I am new here. I am trying to get my first private server. But the project tera-client-packer is taking a lot of time.
Has anyone encounter this problem?
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by hsdn
I have good news for everyone!
In the near future, the full implementation of TERA Shop with promocode functions and Admin Panel for Tera API (management of the shop, accounts, bans, server list, maintenance, etc) will be published. The TERA Shop is part of the Tera API.
That looks wonderful! I now want that UI for the normal WebApp site. It's really awesome with the item templates showing the picture and such too. Looking forward to the update!
Question for ya.
Is there a way to have a local IP based login, or some way to have a local IP for a server? Either through a launcher flag (like the url it hits). I have my world set using the public IP so my friends can connect, but for me in my house I'd like to have the world with the local IP so I don't need to make the hops around the internet. It looks like the login/world list stuff is all on the API side right? So perhaps a subnet mask can be added to the config (or reading the network adapter in use), and the local IP as well. So anything matching that mask will just get the local IP returned to the client instead of what's in the world db (server_info table). Followup would be adding a cert (like with Certbot from LetsEncrypt) for launcher login, but that's not a big deal for now.
07-07-22
hsdn
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by angerthosenear
Is there a way to have a local IP based login, or some way to have a local IP for a server?
This is not an API issue. I also use an external IP address for my server, but that doesn't stop me from connect to it from my LAN. To do this, you need to configure routing to your external IP from your local network (read about Hairpin NAT technology).
Quote:
Originally Posted by angerthosenear
Followup would be adding a cert (like with Certbot from LetsEncrypt) for launcher login, but that's not a big deal for now.
It is assumed that you will use the API behind a proxy web server with a certificate (for example, nginx with certbot).
07-07-22
angerthosenear
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by hsdn
This is not an API issue. I also use an external IP address for my server, but that doesn't stop me from connect to it from my LAN. To do this, you need to configure routing to your external IP from your local network (read about Hairpin NAT technology).
Fair. My setup is a bit weird. See here: https://forum.ragezone.com/f797/tera...ml#post9132748
The public IP for my server is not the public IP for my network since I'm using a cloud VPS and VPN to the server to get the ports punched through. I'll see if I can get a hairpin NAT style rule on my router (UDM Pro), but it is a bit more unusual since the IP doesn't match that of the router. Will give it a whirl, but hopefully that clears up why I asked.
Quote:
Originally Posted by hsdn
It is assumed that you will use the API behind a proxy web server with a certificate (for example, nginx with certbot).
Cool, that's mostly what I figured would be the way to do so, just wanted to be sure.
07-07-22
hexaDoc
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by angerthosenear
Fair. My setup is a bit weird. See here: https://forum.ragezone.com/f797/tera...ml#post9132748
The public IP for my server is not the public IP for my network since I'm using a cloud VPS and VPN to the server to get the ports punched through. I'll see if I can get a hairpin NAT style rule on my router (UDM Pro), but it is a bit more unusual since the IP doesn't match that of the router. Will give it a whirl, but hopefully that clears up why I asked.
Cool, that's mostly what I figured would be the way to do so, just wanted to be sure.
On my side, my router doesn't handle IP loopback, so what I did is having two serverlist, one with public IP, and another one with direct LAN IP. Could work for you too.
08-07-22
angerthosenear
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by hexaDoc
On my side, my router doesn't handle IP loopback, so what I did is having two serverlist, one with public IP, and another one with direct LAN IP. Could work for you too.
Oh, that's a great idea. Is this a matter of making serverId not the primary key in the server_info table, having a duplicate row in that table but with a different loginIp and nameString?
08-07-22
hsdn
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by angerthosenear
Oh, that's a great idea. Is this a matter of making serverId not the primary key in the server_info table, having a duplicate row in that table but with a different loginIp and nameString?
Removing the primary key can cause a problem when working with the api admin panel and SLS generator algo.
But you can just add a server with a different id to the list, like 2801, it will work fine.
08-07-22
angerthosenear
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by hsdn
Removing the primary key can cause a problem when working with the api admin panel and SLS generator algo.
But you can just add a server with a different id to the list, like 2801, it will work fine.
I feared something like that which is why I asked. I thought a different id would cause issues when connecting, like trying to point at PlanetDB_2801.
Tested it out and it works great. Thanks!
08-07-22
hsdn
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Having slight problem updating the launcher, if anyone could help.
1. Made new launcher and put it in public/patch/launcher_update directory as LauncherInstaller_1.0.1.52.exe (even though this is just the launcher, not a setup file. Tried this also with a setup file made for the new launcher)
2. Edited launcher_info.ini in public/patch with version=1.0.1.52 and url pointing at http//localhost/tera-api/public/patch/launcher_update/LauncherInstaller_1.0.1.52.exe
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by MasterRow
Having slight problem updating the launcher, if anyone could help.
1. Made new launcher and put it in public/patch/launcher_update directory as LauncherInstaller_1.0.1.52.exe (even though this is just the launcher, not a setup file. Tried this also with a setup file made for the new launcher)
2. Edited launcher_info.ini in public/patch with version=1.0.1.52 and url pointing at http//localhost/tera-api/public/patch/launcher_update/LauncherInstaller_1.0.1.52.exe
Check API console when you receive this error.
Usually the API shows the path to the file he's trying to get, it will look something like this (404/Path not found) or something similar and it will show you the path, so try to work from there.
I've had the same issue when i had my API setted up so every error i manged to fix it via API Console (LIVE LOGS).
After you get the path just check if the file its actually there because for me some files weren't in the right folder.
Hope it helps you, post here again if you need something else, have a good day!
10-07-22
MasterRow
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Quote:
Originally Posted by S37uP!Update
Check API console when you receive this error.
Usually the API shows the path to the file he's trying to get, it will look something like this (404/Path not found) or something similar and it will show you the path, so try to work from there.
I've had the same issue when i had my API setted up so every error i manged to fix it via API Console (LIVE LOGS).
After you get the path just check if the file its actually there because for me some files weren't in the right folder.
Hope it helps you, post here again if you need something else, have a good day!
Had wrong path in info.ini. Updated to the default path of /public/patch per the .env instead of changing it and all working.
Thanks for the reply.
11-07-22
vazabisong
Re: Tera API (node.js) and Launcher with pacher for patch 92/100
Full implementation of Admin Panel for API features and Tera Shop.
Added language select in the Launcher.
Implementation of the promo code system (Tera Shop).
New server availability check algorithm.
Integration with the Steer Server and Tera Platform Hub.
The use of FCGI WebAPI and FCGI Gateway is no longer required.
Automatic creation of Service Items (Box).
Improve application console logging and debugging.
Now a single database for the API is used.
Lots of improvements and fixes.
Admin Panel features:
User accounts management.
Account benefits management.
User bans management (including IP bans).
Monitoring of online users with kick functions.
SLS (server list) management with server check.
Server list strings management.
Server maintenance plans management.
Full management of the Tera Shop and promo codes system.
Functions for sending the Item Claim boxes.
Admin tasks management (background queue).
View logs of API, Shop and boxes.
View detailed admin operations log.
How to install an update
Spoiler:
Important! We removed database separation, now all tables used by the API are in one database, so if you used a separate database for reports, you need to import it into the accountdb database.
All steps are strictly required!
Replace the file package.json with new one and run install.bat file.
Completely delete the src directory and add it with a new one from the update.
Replace all files in the public\launcher directory with new ones.
Replace all files in the config directory with new ones (make your own settings if necessary).
Unpack the share\data\tera-icons.zip archive to tera-api\data\tera-icons folder.
Import the database structure from the share\db\00_schema.sql file (new tables will be added).
Import the database updates from the share\db\updates\00_update.sql.
If you get errors while importing the 00_update.sql, run the queries from the file manually one by one, ignoring the queries with errors. This step not required for new installations or clean database!
Import other database files from the share\db directory for the Shop, Item Claim and other features to work. Example data of Tera Shop (with most items) is in file 03_db_shop_data.sql.
Many paramenets in the .env file have been changed, so you can copy the new .env.example file to .env and make your own settings.
Open config\admin.js file and change URLs for Admin Panel Quick Menu links.
By default, the admin panel is available on all IP addresses at port 8050, like http://127.0.0.1:8050. You can change this in the .env settings. To enter the admin panel, use login apiadmin and password password. These credentials should be used only for tests, and in production you need to set up integration with the Steer Server.
If you get an error when starting the Launcher, clear the Internet Explorer cache.
The Steer Server allows you to flexibly manage permissions to certain sections of the TERA API Admin Panel. For example, you can create a new user and connect it to user group API_AdminPanel_Shop. Users in this group will only have access to Shop management functions. You can also create your own function group.
Enabling TERA Shop and Item Claim Features
Spoiler:
TERA Shop products are configured through the TERA API Admin Panel. The creation of a Service Item in the Box System occurs automatically when a product is added (using the Platform Hub).
@argeus9900_update.sql adds new fields and keys to some database tables, without which some API functions will not work. Load requests to Navicat/HeidiSQL and execute them one by one, ignoring queries with errors (because you already have these keys).
I execute queries from 00_update.sql on clean DB from previous version of API. All queries are completed without any errors: https://i.imgur.com/0Qiv3aD.png
You must complete these queries only once. Re-execution will result in an error. I did not write a script or migration algo to automate this procedure, because it is a very simple operation to understand.
06-08-22
argeus99
Quote:
Originally Posted by hsdn
@argeus9900_update.sql adds new fields and keys to some database tables, without which some API functions will not work. Load requests to Navicat/HeidiSQL and execute them one by one, ignoring queries with errors (because you already have these keys).
I execute queries from 00_update.sql on clean DB from previous version of API. All queries are completed without any errors: https://i.imgur.com/0Qiv3aD.png
You must complete these queries only once. Re-execution will result in an error. I did not write a script or migration algo to automate this procedure, because it is a very simple operation to understand.
Ah, i just figure out what i did....i feel so dumb.... i created a clean db, i did not reuse the existing one that's why it not worked at first try
06-08-22
hsdn
If you are using a clean database from 00_db_schema.sql, you do not need to install 00_update.sql. This file is only needed to upgrade the database from a previous version of the API. This is not required for new installations.
06-08-22
hsdn
Quote:
Originally Posted by argeus99
Now i'm trying to log in and i'm getting the following error
"REGION" is not defined
Make sure you update all launcher files (public\launcher folder). Also you need to clear Internet Explorer cache.
06-08-22
hsdn
Quote:
Originally Posted by argeus99
Yes, i did a clean of public\launcher and src like you said
1. Replace the file package.json with new one and run install.bat file. ✔
2. Completely delete the src directory and add it with a new one from the update. ✔
3. Replace all files in the public\launcher directory with new ones. ✔
4. Replace all files in the config directory with new ones (make your own settings if necessary). ✔
Cleaned inet cache from inetcpl.cpl (i do not have IExplorer - Win11) and still get the 404 from POST /tera/LauncherLoginForm?lang=en
The /tera/LauncherLoginForm page should not be made a POST request. This is a login page, requested by launcher on GET request.
06-08-22
hsdn
Try install latest version of src\app.js from github with disabled cache.
06-08-22
hsdn
A similar error can occur if the launcher javascript does not work (the form is simply submitted directly, without javascript, which is incorrect behavior). It's a cache problem anyway, because in the new version of the API, the authorization scheme has been changed.
06-08-22
hsdn
Quote:
Originally Posted by argeus99
The app.js i have is the same, anyways i redownloaded and place everything again and still nothing
If you are using a clean database from 00_db_schema.sql, you do not need to install 00_update.sql. This file is only needed to upgrade the database from a previous version of the API. This is not required for new installations.
Yep, when you said "from previous version of API" i just figure out why the hell it not worked for me, i just wanted to start with a clean db ignoring the first sentence of "update"
Now i'm trying to log in and i'm getting the following error
Make sure you update all launcher files (public\launcher folder). Also you need to clear Internet Explorer cache.
Yes, i did a clean of public\launcher and src like you said
1. Replace the file package.json with new one and run install.bat file. ✔
2. Completely delete the src directory and add it with a new one from the update. ✔
3. Replace all files in the public\launcher directory with new ones. ✔
4. Replace all files in the config directory with new ones (make your own settings if necessary). ✔
Cleaned inet cache from inetcpl.cpl (i do not have IExplorer - Win11) and still get the 404 from POST /tera/LauncherLoginForm?lang=en
[2022-08-06 22:04:46.816] (info) Arbiter API: POST /authApi/RequestAuthkey 200 - 3.487 ms
[2022/08/06 22:04:47.124] (info) Portal API: GET /tera/ShopAuth?authKey=7cee7cbe-1111-4fc8-1111-e63db1018387 302 - 3.374 ms
[2022/08/06 22:04:47.137] (info) Portal API: GET /tera/ShopMain 200 - 3.117 ms
There's no request in both API/arb_gw
Spoiler:
Code:
[2022/08/06 09:48:26.447] build : Sep 16 2020, 17:25:33, LOG_LEVEL : 5
[2022/08/06 09:48:26.447] Process URL [http://127.0.0.1:8080/api]
[2022/08/06 09:48:26.463] Host: [127.0.0.1] Port: 8080 /api/
[2022/08/06 09:48:26.463] Resolving result 127.0.0.1:8080
[2022/08/06 09:48:26.463] Process URL [http://127.0.0.1:8080/]
[2022/08/06 09:48:26.479] Host: [127.0.0.1] Port: 8080 /
[2022/08/06 09:48:26.479] Resolving result 127.0.0.1:8080
[2022/08/06 09:48:26.479] Start request to host [127.0.0.1:8080] 9ddf94
[2022/08/06 09:48:26.479] REST Socket closed. Reconnect [9ddf94]
[2022/08/06 09:48:26.494] Host: [127.0.0.1] Port: 8080
[2022/08/06 09:48:26.494] Resolving result 127.0.0.1:8080
[2022/08/06 09:48:26.557] Http result: 200, Size: 15, Error: 0 [9ddf94]
[2022/08/06 09:48:26.572] RequestAPIServerStatusAvailable {"Return":true}
[2022/08/06 09:48:26.572] Start request to host [127.0.0.1:8080] 9de834
[2022/08/06 09:48:26.572] REST Socket closed. Reconnect [9de834]
[2022/08/06 09:48:26.572] Host: [127.0.0.1] Port: 8080
[2022/08/06 09:48:26.572] Resolving result 127.0.0.1:8080
[2022/08/06 09:48:26.588] Http result: 200, Size: 46, Error: 0 [9de834]
[2022/08/06 09:48:26.588] ServiceTest {"result_code":0,"server_time":1659797306.588}
[2022/08/06 09:48:26.604] REST test passed
[2022/08/06 09:48:26.604] Wait for arbiter on port 10001
Server ready
[2022/08/06 09:50:05.016] 9 bytes read on 11c
[2022/08/06 09:50:05.025] Arbiter 2800 connected
[2022/08/06 09:50:05.027] GetServerPermission post data : {"server_id":2800,"serviceCode":"PCO012"}
[2022/08/06 09:50:05.032] Start request to host [127.0.0.1:8080] 9de834
[2022/08/06 09:50:05.043] REST keep-alive timeout. disconnect connection
[2022/08/06 09:50:05.051] REST Socket closed. Reconnect [9de834]
[2022/08/06 09:50:05.056] Host: [127.0.0.1] Port: 8080
[2022/08/06 09:50:05.060] Resolving result 127.0.0.1:8080
[2022/08/06 09:50:05.089] Http result: 200, Size: 32, Error: 0 [9de834]
[2022/08/06 09:50:05.097] GetServerPermission {"result_code":0,"permission":0}
[2022/08/06 09:50:05.103] Server stat 00000000
[2022/08/06 09:50:05.106] Hub 127.0.0.1:11001 connected
[2022/08/06 09:50:05.110] 9 bytes written on 128
[2022/08/06 09:50:05.114] 6 bytes read on 128
[2022/08/06 09:50:05.118] Server registered with 0:2800
[2022/08/06 09:50:05.133] Timezone value 18000
[2022/08/06 09:50:05.136] Handler for class UserLoginReq registered
[2022/08/06 09:50:05.140] Handler for class UserLogoutReq registered
[2022/08/06 09:50:05.147] Handler for class QueryUserReq registered
[2022/08/06 09:50:05.152] Handler for class StartChargeUserReq registered
[2022/08/06 09:50:05.156] Handler for class SendCommandUserReq registered
[2022/08/06 09:50:05.162] Handler for class SendCommandUserAns registered
[2022/08/06 09:50:05.166] Handler for class SendMessageAns registered
[2022/08/06 09:50:05.169] Handler for class DumpUserAns registered
[2022/08/06 09:50:05.171] Handler for class SvrMsgReq registered
[2022/08/06 09:50:05.174] Handler for class QueryShopInfoReq registered
[2022/08/06 09:50:05.180] 11 bytes written on 11c
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:51:05.200] GetServerPermission post data : {"server_id":2800,"serviceCode":"PCO012"}
[2022/08/06 10:00:05.303] Start request to host [127.0.0.1:8080] 9de834
[2022/08/06 10:00:05.303] REST keep-alive timeout. disconnect connection
[2022/08/06 10:00:05.303] REST Socket closed. Reconnect [9de834]
[2022/08/06 10:00:05.318] Host: [127.0.0.1] Port: 8080
[2022/08/06 10:00:05.318] Resolving result 127.0.0.1:8080
[2022/08/06 10:00:05.334] Http result: 200, Size: 32, Error: 0 [9de834]
[2022/08/06 10:00:05.334] GetServerPermission {"result_code":0,"permission":0}
[2022/08/06 10:00:05.334] Server stat 00000000
[2022/08/06 10:01:05.323] GetServerPermission post data : {"server_id":2800,"serviceCode":"PCO012"}
[2022-08-06 22:04:46.816] (info) Arbiter API: POST /authApi/RequestAuthkey 200 - 3.487 ms
[2022/08/06 22:04:47.124] (info) Portal API: GET /tera/ShopAuth?authKey=7cee7cbe-1111-4fc8-1111-e63db1018387 302 - 3.374 ms
[2022/08/06 22:04:47.137] (info) Portal API: GET /tera/ShopMain 200 - 3.117 ms
There's no shop request in the log from api/arb_gw
Spoiler:
Code:
[2022/08/06 09:48:26.447] build : Sep 16 2020, 17:25:33, LOG_LEVEL : 5
[2022/08/06 09:48:26.447] Process URL [http://127.0.0.1:8080/api]
[2022/08/06 09:48:26.463] Host: [127.0.0.1] Port: 8080 /api/
[2022/08/06 09:48:26.463] Resolving result 127.0.0.1:8080
[2022/08/06 09:48:26.463] Process URL [http://127.0.0.1:8080/]
[2022/08/06 09:48:26.479] Host: [127.0.0.1] Port: 8080 /
[2022/08/06 09:48:26.479] Resolving result 127.0.0.1:8080
[2022/08/06 09:48:26.479] Start request to host [127.0.0.1:8080] 9ddf94
[2022/08/06 09:48:26.479] REST Socket closed. Reconnect [9ddf94]
[2022/08/06 09:48:26.494] Host: [127.0.0.1] Port: 8080
[2022/08/06 09:48:26.494] Resolving result 127.0.0.1:8080
[2022/08/06 09:48:26.557] Http result: 200, Size: 15, Error: 0 [9ddf94]
[2022/08/06 09:48:26.572] RequestAPIServerStatusAvailable {"Return":true}
[2022/08/06 09:48:26.572] Start request to host [127.0.0.1:8080] 9de834
[2022/08/06 09:48:26.572] REST Socket closed. Reconnect [9de834]
[2022/08/06 09:48:26.572] Host: [127.0.0.1] Port: 8080
[2022/08/06 09:48:26.572] Resolving result 127.0.0.1:8080
[2022/08/06 09:48:26.588] Http result: 200, Size: 46, Error: 0 [9de834]
[2022/08/06 09:48:26.588] ServiceTest {"result_code":0,"server_time":1659797306.588}
[2022/08/06 09:48:26.604] REST test passed
[2022/08/06 09:48:26.604] Wait for arbiter on port 10001
Server ready
[2022/08/06 09:50:05.016] 9 bytes read on 11c
[2022/08/06 09:50:05.025] Arbiter 2800 connected
[2022/08/06 09:50:05.027] GetServerPermission post data : {"server_id":2800,"serviceCode":"PCO012"}
[2022/08/06 09:50:05.032] Start request to host [127.0.0.1:8080] 9de834
[2022/08/06 09:50:05.043] REST keep-alive timeout. disconnect connection
[2022/08/06 09:50:05.051] REST Socket closed. Reconnect [9de834]
[2022/08/06 09:50:05.056] Host: [127.0.0.1] Port: 8080
[2022/08/06 09:50:05.060] Resolving result 127.0.0.1:8080
[2022/08/06 09:50:05.089] Http result: 200, Size: 32, Error: 0 [9de834]
[2022/08/06 09:50:05.097] GetServerPermission {"result_code":0,"permission":0}
[2022/08/06 09:50:05.103] Server stat 00000000
[2022/08/06 09:50:05.106] Hub 127.0.0.1:11001 connected
[2022/08/06 09:50:05.110] 9 bytes written on 128
[2022/08/06 09:50:05.114] 6 bytes read on 128
[2022/08/06 09:50:05.118] Server registered with 0:2800
[2022/08/06 09:50:05.133] Timezone value 18000
[2022/08/06 09:50:05.136] Handler for class UserLoginReq registered
[2022/08/06 09:50:05.140] Handler for class UserLogoutReq registered
[2022/08/06 09:50:05.147] Handler for class QueryUserReq registered
[2022/08/06 09:50:05.152] Handler for class StartChargeUserReq registered
[2022/08/06 09:50:05.156] Handler for class SendCommandUserReq registered
[2022/08/06 09:50:05.162] Handler for class SendCommandUserAns registered
[2022/08/06 09:50:05.166] Handler for class SendMessageAns registered
[2022/08/06 09:50:05.169] Handler for class DumpUserAns registered
[2022/08/06 09:50:05.171] Handler for class SvrMsgReq registered
[2022/08/06 09:50:05.174] Handler for class QueryShopInfoReq registered
[2022/08/06 09:50:05.180] 11 bytes written on 11c
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:51:05.200] GetServerPermission post data : {"server_id":2800,"serviceCode":"PCO012"}
[2022/08/06 10:00:05.303] Start request to host [127.0.0.1:8080] 9de834
[2022/08/06 10:00:05.303] REST keep-alive timeout. disconnect connection
[2022/08/06 10:00:05.303] REST Socket closed. Reconnect [9de834]
[2022/08/06 10:00:05.318] Host: [127.0.0.1] Port: 8080
[2022/08/06 10:00:05.318] Resolving result 127.0.0.1:8080
[2022/08/06 10:00:05.334] Http result: 200, Size: 32, Error: 0 [9de834]
[2022/08/06 10:00:05.334] GetServerPermission {"result_code":0,"permission":0}
[2022/08/06 10:00:05.334] Server stat 00000000
[2022/08/06 10:01:05.323] GetServerPermission post data : {"server_id":2800,"serviceCode":"PCO012"}
I think the problem is on the tera server side. After you commented out the line in DeploymentConfig.xml, the server should using the link from config_arb_gw.txt to open the Shop on client. Try to completely restart all server components.
07-08-22
MentaL
Quote:
Originally Posted by argeus99
There's no request in both API/arb_gw
Spoiler:
Code:
[2022/08/06 09:48:26.447] build : Sep 16 2020, 17:25:33, LOG_LEVEL : 5
[2022/08/06 09:48:26.447] Process URL [http://127.0.0.1:8080/api]
[2022/08/06 09:48:26.463] Host: [127.0.0.1] Port: 8080 /api/
[2022/08/06 09:48:26.463] Resolving result 127.0.0.1:8080
[2022/08/06 09:48:26.463] Process URL [http://127.0.0.1:8080/]
[2022/08/06 09:48:26.479] Host: [127.0.0.1] Port: 8080 /
[2022/08/06 09:48:26.479] Resolving result 127.0.0.1:8080
[2022/08/06 09:48:26.479] Start request to host [127.0.0.1:8080] 9ddf94
[2022/08/06 09:48:26.479] REST Socket closed. Reconnect [9ddf94]
[2022/08/06 09:48:26.494] Host: [127.0.0.1] Port: 8080
[2022/08/06 09:48:26.494] Resolving result 127.0.0.1:8080
[2022/08/06 09:48:26.557] Http result: 200, Size: 15, Error: 0 [9ddf94]
[2022/08/06 09:48:26.572] RequestAPIServerStatusAvailable {"Return":true}
[2022/08/06 09:48:26.572] Start request to host [127.0.0.1:8080] 9de834
[2022/08/06 09:48:26.572] REST Socket closed. Reconnect [9de834]
[2022/08/06 09:48:26.572] Host: [127.0.0.1] Port: 8080
[2022/08/06 09:48:26.572] Resolving result 127.0.0.1:8080
[2022/08/06 09:48:26.588] Http result: 200, Size: 46, Error: 0 [9de834]
[2022/08/06 09:48:26.588] ServiceTest {"result_code":0,"server_time":1659797306.588}
[2022/08/06 09:48:26.604] REST test passed
[2022/08/06 09:48:26.604] Wait for arbiter on port 10001
Server ready
[2022/08/06 09:50:05.016] 9 bytes read on 11c
[2022/08/06 09:50:05.025] Arbiter 2800 connected
[2022/08/06 09:50:05.027] GetServerPermission post data : {"server_id":2800,"serviceCode":"PCO012"}
[2022/08/06 09:50:05.032] Start request to host [127.0.0.1:8080] 9de834
[2022/08/06 09:50:05.043] REST keep-alive timeout. disconnect connection
[2022/08/06 09:50:05.051] REST Socket closed. Reconnect [9de834]
[2022/08/06 09:50:05.056] Host: [127.0.0.1] Port: 8080
[2022/08/06 09:50:05.060] Resolving result 127.0.0.1:8080
[2022/08/06 09:50:05.089] Http result: 200, Size: 32, Error: 0 [9de834]
[2022/08/06 09:50:05.097] GetServerPermission {"result_code":0,"permission":0}
[2022/08/06 09:50:05.103] Server stat 00000000
[2022/08/06 09:50:05.106] Hub 127.0.0.1:11001 connected
[2022/08/06 09:50:05.110] 9 bytes written on 128
[2022/08/06 09:50:05.114] 6 bytes read on 128
[2022/08/06 09:50:05.118] Server registered with 0:2800
[2022/08/06 09:50:05.133] Timezone value 18000
[2022/08/06 09:50:05.136] Handler for class UserLoginReq registered
[2022/08/06 09:50:05.140] Handler for class UserLogoutReq registered
[2022/08/06 09:50:05.147] Handler for class QueryUserReq registered
[2022/08/06 09:50:05.152] Handler for class StartChargeUserReq registered
[2022/08/06 09:50:05.156] Handler for class SendCommandUserReq registered
[2022/08/06 09:50:05.162] Handler for class SendCommandUserAns registered
[2022/08/06 09:50:05.166] Handler for class SendMessageAns registered
[2022/08/06 09:50:05.169] Handler for class DumpUserAns registered
[2022/08/06 09:50:05.171] Handler for class SvrMsgReq registered
[2022/08/06 09:50:05.174] Handler for class QueryShopInfoReq registered
[2022/08/06 09:50:05.180] 11 bytes written on 11c
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:51:05.200] GetServerPermission post data : {"server_id":2800,"serviceCode":"PCO012"}
[2022/08/06 10:00:05.303] Start request to host [127.0.0.1:8080] 9de834
[2022/08/06 10:00:05.303] REST keep-alive timeout. disconnect connection
[2022/08/06 10:00:05.303] REST Socket closed. Reconnect [9de834]
[2022/08/06 10:00:05.318] Host: [127.0.0.1] Port: 8080
[2022/08/06 10:00:05.318] Resolving result 127.0.0.1:8080
[2022/08/06 10:00:05.334] Http result: 200, Size: 32, Error: 0 [9de834]
[2022/08/06 10:00:05.334] GetServerPermission {"result_code":0,"permission":0}
[2022/08/06 10:00:05.334] Server stat 00000000
[2022/08/06 10:01:05.323] GetServerPermission post data : {"server_id":2800,"serviceCode":"PCO012"}
There's no shop request in the log from api/arb_gw
Spoiler:
Code:
[2022/08/06 09:48:26.447] build : Sep 16 2020, 17:25:33, LOG_LEVEL : 5
[2022/08/06 09:48:26.447] Process URL [http://127.0.0.1:8080/api]
[2022/08/06 09:48:26.463] Host: [127.0.0.1] Port: 8080 /api/
[2022/08/06 09:48:26.463] Resolving result 127.0.0.1:8080
[2022/08/06 09:48:26.463] Process URL [http://127.0.0.1:8080/]
[2022/08/06 09:48:26.479] Host: [127.0.0.1] Port: 8080 /
[2022/08/06 09:48:26.479] Resolving result 127.0.0.1:8080
[2022/08/06 09:48:26.479] Start request to host [127.0.0.1:8080] 9ddf94
[2022/08/06 09:48:26.479] REST Socket closed. Reconnect [9ddf94]
[2022/08/06 09:48:26.494] Host: [127.0.0.1] Port: 8080
[2022/08/06 09:48:26.494] Resolving result 127.0.0.1:8080
[2022/08/06 09:48:26.557] Http result: 200, Size: 15, Error: 0 [9ddf94]
[2022/08/06 09:48:26.572] RequestAPIServerStatusAvailable {"Return":true}
[2022/08/06 09:48:26.572] Start request to host [127.0.0.1:8080] 9de834
[2022/08/06 09:48:26.572] REST Socket closed. Reconnect [9de834]
[2022/08/06 09:48:26.572] Host: [127.0.0.1] Port: 8080
[2022/08/06 09:48:26.572] Resolving result 127.0.0.1:8080
[2022/08/06 09:48:26.588] Http result: 200, Size: 46, Error: 0 [9de834]
[2022/08/06 09:48:26.588] ServiceTest {"result_code":0,"server_time":1659797306.588}
[2022/08/06 09:48:26.604] REST test passed
[2022/08/06 09:48:26.604] Wait for arbiter on port 10001
Server ready
[2022/08/06 09:50:05.016] 9 bytes read on 11c
[2022/08/06 09:50:05.025] Arbiter 2800 connected
[2022/08/06 09:50:05.027] GetServerPermission post data : {"server_id":2800,"serviceCode":"PCO012"}
[2022/08/06 09:50:05.032] Start request to host [127.0.0.1:8080] 9de834
[2022/08/06 09:50:05.043] REST keep-alive timeout. disconnect connection
[2022/08/06 09:50:05.051] REST Socket closed. Reconnect [9de834]
[2022/08/06 09:50:05.056] Host: [127.0.0.1] Port: 8080
[2022/08/06 09:50:05.060] Resolving result 127.0.0.1:8080
[2022/08/06 09:50:05.089] Http result: 200, Size: 32, Error: 0 [9de834]
[2022/08/06 09:50:05.097] GetServerPermission {"result_code":0,"permission":0}
[2022/08/06 09:50:05.103] Server stat 00000000
[2022/08/06 09:50:05.106] Hub 127.0.0.1:11001 connected
[2022/08/06 09:50:05.110] 9 bytes written on 128
[2022/08/06 09:50:05.114] 6 bytes read on 128
[2022/08/06 09:50:05.118] Server registered with 0:2800
[2022/08/06 09:50:05.133] Timezone value 18000
[2022/08/06 09:50:05.136] Handler for class UserLoginReq registered
[2022/08/06 09:50:05.140] Handler for class UserLogoutReq registered
[2022/08/06 09:50:05.147] Handler for class QueryUserReq registered
[2022/08/06 09:50:05.152] Handler for class StartChargeUserReq registered
[2022/08/06 09:50:05.156] Handler for class SendCommandUserReq registered
[2022/08/06 09:50:05.162] Handler for class SendCommandUserAns registered
[2022/08/06 09:50:05.166] Handler for class SendMessageAns registered
[2022/08/06 09:50:05.169] Handler for class DumpUserAns registered
[2022/08/06 09:50:05.171] Handler for class SvrMsgReq registered
[2022/08/06 09:50:05.174] Handler for class QueryShopInfoReq registered
[2022/08/06 09:50:05.180] 11 bytes written on 11c
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:50:05.182] Entering Main loop
[2022/08/06 09:51:05.200] GetServerPermission post data : {"server_id":2800,"serviceCode":"PCO012"}
[2022/08/06 10:00:05.303] Start request to host [127.0.0.1:8080] 9de834
[2022/08/06 10:00:05.303] REST keep-alive timeout. disconnect connection
[2022/08/06 10:00:05.303] REST Socket closed. Reconnect [9de834]
[2022/08/06 10:00:05.318] Host: [127.0.0.1] Port: 8080
[2022/08/06 10:00:05.318] Resolving result 127.0.0.1:8080
[2022/08/06 10:00:05.334] Http result: 200, Size: 32, Error: 0 [9de834]
[2022/08/06 10:00:05.334] GetServerPermission {"result_code":0,"permission":0}
[2022/08/06 10:00:05.334] Server stat 00000000
[2022/08/06 10:01:05.323] GetServerPermission post data : {"server_id":2800,"serviceCode":"PCO012"}
disconnected by client (recv 0 bytes)
AuthManager::OnDisconnectSession [AuthStatus:1] [Account:0000000000000000] [AccountId:0]
disconnected by client (recv 0 bytes)
AuthManager::OnDisconnectSession [AuthStatus:1] [Account:0000000000000000] [AccountId:0]
disconnected by client (recv 0 bytes)
AuthManager::OnDisconnectSession [AuthStatus:1] [Account:0000000000000000] [AccountId:0]
disconnected by client (recv 0 bytes)
AuthManager::OnDisconnectSession [AuthStatus:1] [Account:0000000000000000] [AccountId:0]
disconnected by client (recv 0 bytes)
AuthManager::OnDisconnectSession [AuthStatus:1] [Account:0000000000000000] [AccountId:0]
disconnected by client (recv 0 bytes)
AuthManager::OnDisconnectSession [AuthStatus:1] [Account:0000000000000000] [AccountId:0]
Is that normal?
08-08-22
hsdn
Quote:
Originally Posted by TieLay
In log of Arbiter server strange messages me see:
Is that normal?
You may consider this normal.
This is the result of the server availability port-checker used for non-existent Planet IDs.
Use ID 2800 in your Server List and remove non-existent IDs, then the check server will be done via Platform Hub without direct port checking.
Also you will probably need to install the fix available in the latest update 08.08.2022
(download update and replace the src directory).
Looks like is something related to timezone i guess, because when i create an item via boxserver and use the same time the system gives me it not works, but if i use a time before registered date it works instantly
Is there a way to change the time zone in the boxserver? (i guess that's the problem, because i don't understand why the registered date is different than the activation date)
09-08-22
hsdn
Quote:
Originally Posted by argeus99
Is there a way to change the time zone in the boxserver? (i guess that's the problem, because i dont understand why the registered dates is different than the activation date)
I think the box server and tera server is using OS time, then the API is using UTC time when registering the item. If your time zone is less than UTC, there may be problems.
For fix it, try editing the API file tera-api\src\utils\boxHelper.js and replace all of entries like moment().utc() with moment().
Save file and restart API. If it solve this problem, I make the update (for box and benefits).
09-08-22
argeus99
Quote:
Originally Posted by hsdn
I think the box server and tera server is using OS time, then the API is using UTC time when registering the item. If your time zone is less than UTC, there may be problems.
For fix it, try editing the API file tera-api\src\utils\boxHelper.js and replace all of entries like moment().utc() with moment().
Save file and restart API. If it solve this problem, I make the update (for box and benefits).
@fitnessguy0 Did you add server to server list in admin panel? Also check API log.
OK,it seems like work now...
just wondering can it log into the game without steer and box sever...??because I only have laucher in my server...I mean I don't have tera full client files in my server...so I currently cannot test ..thx