-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can`t start container #153
Comments
Please authorise in interactive mode. It is one time operation. |
After you successfully login you need to stop temporary container and start it in background with "up -d" command. If you need to start multiple sessions, create docker-compose.override.yml. Add additional containers there. Use unique ports and session names in command. You can autorize sessions remotely, but i do not support this function anymore, use it at your own risk: https://github.com/xtrime-ru/TelegramApiServer?tab=readme-ov-file#multiple-sessions-support To enable multi session mode and skip session creation during start use |
Have I just to create file docker-compose.override.yml and just start container like docker compose up -d? Is there anything else? |
I lost session after reload container. Why are sessions not saved? |
Yes. Override port and command, or add new container. |
How you created the session? |
remotely. with link http://IP:9503/system/addSession?session=users/xtrime |
have done all requests to authorize it? https://github.com/xtrime-ru/TelegramApiServer?tab=readme-ov-file#authorizing-session-remotely You could try to call But as i said, i provide no support for this feature... |
ok. thanks a lot |
You need to authorise this session, and make sure its serialized before restarting (call serialize method, or wait 10 minutes before automatic serialization happens) |
Do you mean my session didn't have time to save at vps? But there is file with session on vps. I just stop and start again the container |
http://IP:9521/api/users/number/serialize gives me that error |
Serialization method was moved in other place, probably this is why your session not saved after manual login via http. I pushed fix: 6a045fd Please update to latest master and try to call serizalize again after manual login. |
Dont know anything about |
Everything is from https://github.com/xtrime-ru/TelegramApiServer/tree/master#session-management |
thanks. It works well |
that error goes when I add new session. |
Is you use -s=* it means to load all sessions in container. Please use globe syntax to select sessions for each container: https://en.wikipedia.org/wiki/Glob_(programming) |
Deleting session is complicated. You need to stop container, then remove session folder, then remove session tables from mysql database. |
hi. thanks a lot. But how can I do that (deleting from table)? Is it real only by modifying table with another program or something docker command? |
Hi. I try to start container like it`s written here but it goes to error.
Help me please.
There is the same error with memory usage settings.
That works interactively only
The text was updated successfully, but these errors were encountered: