Posts by mgmarshall

Dear forum members,
for some time now we have been creating and maintaining new ways to help game server admins with questions and problems as quickly as possible, e.g. our Guides section and the Nitrado Community Discord.

Therefore, we inform you that the Nitrado Forum will be closed on March 31, 2023. We are consolidating our community support to our Discord channel, which is faster and more efficient. We have also seen incredible growth in our community due to the hard work of our moderators and our bots. We are confident that this move will ensure that we provide the best support possible for our users.

Thank you to all members for your continued use of the forum!

Assistance with all questions concerning your Nitrado service can now be found in these spots:
Community Discord:
Guides section:
Support Wizard:

    Hey Doagen, thanks for the reply.

    The problem did turn out indeed to be the Nitrado server.

    Replies and fix below.

    Their reply carrying on from above:

    I have been testing this out all day and apart from a slight hiccup at the beginning with me re-installing ARK on the Nitrado server all is going well, so I have just replied with this:

    1. Thank you very much. Although this did not work at first, I performed a RE-INSTALL and then set it up with the previous settings using my locally saved files.
    2. It now works with no problems, thank you for looking into this.
    3. Just to note, I did actually uninstall the games a few times previous to this support request, to try and resolve the problem myself. I definitely got moved to a new IP address at least once, maybe twice. This may have been on the same machine though, but I thought I would let you know as your solution was to move server.

    Anyway all is good, and I think the moral of the story is do your homework, prove as much as you can, provide evidence and be persistent if you are sure you are correct. I knew this was not a software or configuration issue, or I would never have raised the call in the first place. I do however understand that not many people are as thorough as me and that some will probably send a support call at the drop of a hat.

    This is happening to my server too, the support team keep closing my ticket and I keep on opening it... I have done testing and its def the s+ mod and yes I believe its a corrupted file, though I think those files are centrally cached, probably for multiple servers, hence not everyone is seeing the error.

    Full support request below so you can see how rude they are!!

    They replied with this:

    My reply:

    1. I tried this and it did not work. Same issue, and I definitely updated the .mod file. I only have access to the .mod file, the directory does not exist for any of the mods on the Nitrado server.
    2. Also I don't think this is a mod update issue, this mod has not been updated for 6 months.
    3. There was a server update recently that did cause problems to s+ but not like this, just some individual items not working.
    4. I believe this is a Nitrado only issue, perhaps to do with caching.

    Then they started giving me generic replies:

    My reply:

    Then they closed my ticket twice (marked as resolved), and I keep opening it again!

    1. A mistake was made by your systems, this issue is not resolved. Many thanks.
    1. Why does this keep being set as solved? It is not solved, please advise.

    Thats it, all I have.

    There is def an S+ issue, my testing confirms this.

    As I suspected this doesn't apply to all Nitrado customers, or we would hear way more about it. I think its only a handful of the newer servers effected, probably all use the same caching or something.

    Hope this helps someone or gets Nitrado support to stop closing my calls without being resolved!