Jump to content

Harakiric

Members
  • Posts

    3
  • Joined

  • Last visited

Posts posted by Harakiric

  1. On 1/29/2021 at 8:21 AM, ich777 said:

    I have now updated the container, please force an update of the container on the Docker page in Unraid: grafik.png.be15b053c1645caaa6b10f236105ede5.png

     

    You now have the ability to delete the entry 'server.cfg' from the variable 'ConfigFile' and the server will start without the server.cfg and load up the txAdmin, but keep in mind that you have to add another Port entry in the template with the container and host port '40120', also you don't have to set any ConVars since these are only if you want to change the port, the default port for txAdmin is 40120 and you then can connect to you txAdmin console with YOURSERVERIP:40120 attached a few screenshots (will update the template discription shortly):

     

    grafik.thumb.png.f8d29b4027362c575540f78f35450d3e.png

     

    grafik.png.3ddfe648cfeb6a6caeb8cb4c1a40927b.png

     

    grafik.png.e82fcdae0183837f0ffaa794e6e04147.png

     

    grafik.png.5dd3ba43845ac33af4c9ba5960edee78.png

     

    This worked incredibly well, thank you so much!!!

     

    You're the best!

    • Like 1
  2. On 1/21/2021 at 8:14 AM, ich777 said:

    Yes that is possible, according to this page txAdmin is integrated in every FXServer above 2524 and you only have to add '+set txAdminPort 40121' to the start command.

     

    To do that go in your template enter '+set txAdminPort 40121' (without quotes and the port that you preferr - in this case 40121) at 'Start Variables', then you have to also click on 'Add another Path, Port, Variable, Label or Device' and select 'Port' for the Host and Containerport set the above set Port (in this case 40121), click on 'Add' and then on 'Apply'.

    After the Container is fully startup you should be able to connect to txAdmin with YOURSERVERIP:YOURSETPORT

     

    I have tried this but it makes no difference, it still starts up the server immediately instead of txadmin. 

    I think its because the docker runs the "+exec server.cfg" ConVar when launching run.sh

     

    is there a way to launch run.sh without any ConVars?

×
×
  • Create New...