Steam-TS admin panel

[strikerlord]

Once i have the program launched and i go to localhost:8090 (changed the port) and i want to log in it reroutes me back to the login page.
I simply can't seem to log in....

would this be something to do with the Session file store that isn't found?

> steam-ts@1.3.3 start F:\Steam TS\steam-ts-master
> node lib/launch.js

Trying to connect to the TeamSpeak server...
Logged into the query with credentials.
Using virtual server 16 now.
Changed query client name.
Succesfully launched the bot.
Admin panel available on port: 8090
GET / 302 15.848 ms - 56
[session-file-store] will retry, error on last attempt: Error: ENOENT: no such f
ile or directory, open 'F:\Steam TS\steam-ts-master\webserver\sessions\ZDwVmOOHN
tZx3OPg50lmvLpqCMHHsPN9.json'
[session-file-store] will retry, error on last attempt: Error: ENOENT: no such f
ile or directory, open 'F:\Steam TS\steam-ts-master\webserver\sessions\ZDwVmOOHN
tZx3OPg50lmvLpqCMHHsPN9.json'
[session-file-store] will retry, error on last attempt: Error: ENOENT: no such f
ile or directory, open 'F:\Steam TS\steam-ts-master\webserver\sessions\ZDwVmOOHN
tZx3OPg50lmvLpqCMHHsPN9.json'
[session-file-store] will retry, error on last attempt: Error: ENOENT: no such f
ile or directory, open 'F:\Steam TS\steam-ts-master\webserver\sessions\ZDwVmOOHN
tZx3OPg50lmvLpqCMHHsPN9.json'
GET /login 200 241.413 ms - 2849
GET /stylesheets/ie10-viewport-bug-workaround.css 200 79.040 ms - 519
GET /stylesheets/signin.css 200 129.861 ms - 793
GET /stylesheets/sticky-footer.css 200 131.198 ms - 750
GET /stylesheets/toastr.min.css 200 162.860 ms - 5737
GET /stylesheets/bootstrap.min.css 200 166.511 ms - 121260
GET /images/favicon.png 200 118.240 ms - 1492
GET /javascripts/toastr.min.js 200 18.965 ms - 4321
GET /javascripts/ie10-viewport-bug-workaround.js 200 47.157 ms - 641
GET /javascripts/login.js 200 39.875 ms - 2895
GET /javascripts/socket.io-1.4.5.js 200 65.893 ms - 97690
GET /javascripts/jquery.min.js 200 159.355 ms - 84380
GET /fonts/glyphicons-halflings-regular.woff2 200 39.605 ms - 18028
GET / 302 3.336 ms - 56
GET /login 304 3.469 ms - -
GET /stylesheets/bootstrap.min.css 304 0.962 ms - -
GET /stylesheets/ie10-viewport-bug-workaround.css 304 4.606 ms - -
GET /stylesheets/signin.css 304 5.140 ms - -
GET /stylesheets/sticky-footer.css 304 2.465 ms - -
GET /stylesheets/toastr.min.css 304 6.520 ms - -
GET /javascripts/jquery.min.js 304 5.109 ms - -
GET /javascripts/ie10-viewport-bug-workaround.js 304 1.188 ms - -
GET /javascripts/socket.io-1.4.5.js 304 1.756 ms - -
GET /javascripts/toastr.min.js 304 4.326 ms - -
GET /javascripts/login.js 304 5.150 ms - -
GET /images/favicon.png 304 14.924 ms - -
Successfully queried users and updated userdata.
Successfully queried users and updated userdata.
Successfully queried users and updated userdata.

[starwolfy]

Yes, that has to do with the service not being able to locate the session files. Sessions are stored in the /sessions folder, does your service have permission to write and read there? Try CHMOD'ing the project and its files.

[starwolfy]

Turns out to be an issue with Windows. The web interface doesn't seem to work if the service is hosted on a Windows operating system and this has been noted in the README.md .

[strikerlord]

There is a workaround:
as long as you do enough login attempts you will pass through the authentication.
it also helps to switch to another URL for the admin panel and switch back to the login page:
localurl:8080/login - do login attempt - fail - request localurl:8080/index - request localurl:8080/login - try again and repeat as needed.
3 tries usualy does it.

[Owned67]

This doesn't work....

[strikerlord]

This doesn't work....

Hmmm, even after I migrated it to a Server 2019 evaluation copy this worked (better even) on Firefox.
Different browsers do tent to give different results on that.