That's not my problem that's your server dying because you're creating a 5GB container.
What you've said else is your problem i did not share XUI admin panel or full panel working 100%, i shared a custom build of working xtream-ui now i set it up, and i created a test user i also tested live stream of m3u8 links and it was working, what happens after that is really not my response because you can edit or replace admin files anytime after you purchase click "go to download" and read the page it tells you how to access xtream-ui files
mysql infos are into container at /root/MYSQL_INFO or you can simply decrypt config file.
At the end you and everyone else should keep in mind that my point was to make XUI available on Docker Container and not to share a working xtream-ui copy.
I read everything you posted about this docker config previous to allowing the 10 credits to download and try it out. Which even before sending the 10 credits I already had the git location open and the Container setup. Not because I was trying to get around applying the credits, I actually found the install location for this before I read this post at all, I came across it from a random docker catalog search a few days ago. The instructions posted on the page ended in error on initial attempt at install due to a conflict with the version reference made in the yml. That was simple enough to correct and upon doing so the rest of the install proceeded without any issues.
I then came across you post in this forum searching for a solution to one of the issues mentioned above and saw where you offered your voice in reference to your custom container for a small asking quota to which I was happy to oblige. Since my registration to this forum is relatively new, I had to follow the guidelines presented and do my part to establish my profile enough to collect 10 credits so to speak with you, which took about 24 hours in bits here and there reading over other posts and getting to know the forum a bit more which was well worth the time.
All that being said, I'd like to once again try to explain the direction I attempted to approach you with earlier but in a more descriptive context as which to explain why I imagined my question to you would fit the grounds mentioned by you as which were appropriate to contact for help.
As mentioned before I have previously setup a normal XUI admin panel from scratch and it is still being managed in a functional state so I understand the basics of it. I thought the idea of a docker based panel could be beneficial in many ways, which is why I first located your install page from my global catalog search after researching the thought I had. Rather then attempt to build the docker panel from scratch I wanted to attempt to deploy a pre-built 3rd party build for the reason that this is the major feature I was interested in by using docker in the first place. I wanted to see if, after building my own docker setup from scratch I could then use my build as a base model to deploy them in various stages of functional states to other users.
Rather then waste time with trial and error in the attempt of something I'd never tried before to have a possible negative end result, I wanted to test on a prebuilt model that was in any various stage of functionality so to save precious time as I am a person of many many ongoing projects at once all the time.
My only question to you that I wished to have answered applied to the way the data was being stored in this particular xtream-ui panel that "you" created. I figured since you created it, you would be the best ear to voice a response to my question.
I compared the config files between the normal fully functional xstream-ui panel that I set up to the config of your docker approach side by side and although there are obvious differences, I do not see any that would cause the issue that I am having, which pertains any saved changes I make to the panel only staying with the panel for current instance until the nginx service is restarted, the only changes I have tried are setting up a couple new users and changing the admin password from default to my own, that's all I've attempted to change nothing else.
The change to the admin password works, I can logout and back in with it, but as soon as I restart the nginx serivce from ssh/restart the docker service, and return to login with my new credentials, they no longer work and have been reset to default. The latter, the new users I setup, first, although showing in the manage users category after setup as active, they credentials made for them never work for any panel related functions as they do with the same setup in my other personal panel. Furthermore just like the admin credentials, upon restarting the docker serivce, the new users I made no longer exist in the panel, the only that maintains is the test123 user that you created on build. That user also works for panel related functions.
THE REASON that I considered this a question that fit the bill of your reasoning for asking you questions as mentioned in the post for this in the first place is because none of these occurrences I am having are regular to any other xstream-ui build that I have seen. They all seem to be unique to your build.
I am familiar with mysql and php and understand that stored information/credentials are saved in the mysql db that's why I was asking if you had some abnormal mysql config that I .. HAVE NOT been able to locate. As I looked in all the normal locations for the config and also after your last response in the location that you mentioned and none of those locations hold the config files needed. That's why I asked if you had changed the default mysql password or user on this build because if nothing else with that information I can login and correct it manually.
I didn't expect or ask for a turnkey panel when I installed this. I just need a little info as to if there was any out of the ordinary settings or config changes that you may have made while setting this "custom" panel up as I have tried and cannot replicate the issues on my personal build and there is no errors to speak of in the logs to reference.
Thanks,
as i am not a docker user as you might have noticed
