RCON Remote Connection

[scherzbolds]

It is not really a issue but the question took me years ;)

How the remote works

How to connect and use RCON

In Remote URL enter http://servers_ip_address/
In Security Key enter the servers security key **(This key needs to be exactly 8 characters long**)
In Port, enter the RCON Port from your control panel
Hit “save” then “connect”

[mmmaxwwwell]

Did you get it working with the dedicated server running in docker?

[scherzbolds]

Yes as i used 8 digit passwort it worked perfectly Von: mmmaxwwwell ***@***.***> Gesendet: Donnerstag, 17. Februar 2022 04:27 An: mmmaxwwwell/space-engineers-dedicated-docker-linux ***@***.***> Cc: scherzbolds ***@***.***>; Author ***@***.***> Betreff: Re: [mmmaxwwwell/space-engineers-dedicated-docker-linux] RCON Remote Connection (Issue #36) Did you get it working with the dedicated server? — Reply to this email directly, view it on GitHub <#36 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXZ2Z5NL2IOUYZOVQWOPBT3U3RTGRANCNFSM5OTOMDFA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mmmaxwwwell]

Really appreciate you taking the time to educate us on how to use this. I'll be adding your name to the shoutouts section of the readme.

I'll also update the readme to help clarify this for other players. I know this has stumped quite a few people in the past, including myself. I'll close this issue when that update goes through.

Again, can't say thank you enough for taking the time to educate us.

[scherzbolds]

No problem i loved to use your easy to install guide and program and when i found this information and its helpful for you and others then it makes me smile, happy and thankful for you. Von: mmmaxwwwell ***@***.***> Gesendet: Donnerstag, 17. Februar 2022 23:43 An: mmmaxwwwell/space-engineers-dedicated-docker-linux ***@***.***> Cc: scherzbolds ***@***.***>; Author ***@***.***> Betreff: Re: [mmmaxwwwell/space-engineers-dedicated-docker-linux] RCON Remote Connection (Issue #36) Really appreciate you taking the time to educate us on how to use this. I'll be adding your name to the shoutouts section of the readme. I'll also update the readme to help clarify this for other players. I know this has stumped quite a few people in the past, including myself. I'll close this issue when that update goes through. Again, can't say thank you enough for taking the time to educate us. — Reply to this email directly, view it on GitHub <#36 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXZ2Z5KGIIB2JP2FWXVAMFLU3V2VVANCNFSM5OTOMDFA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Scaff31]

Yes as i used 8 digit passwort it worked perfectly Von: mmmaxwwwell @.> Gesendet: Donnerstag, 17. Februar 2022 04:27 An: mmmaxwwwell/space-engineers-dedicated-docker-linux @.> Cc: scherzbolds @.>; Author @.> Betreff: Re: [mmmaxwwwell/space-engineers-dedicated-docker-linux] RCON Remote Connection (Issue #36) Did you get it working with the dedicated server? — Reply to this email directly, view it on GitHub <#36 (comment)> , or unsubscribe https://github.com/notifications/unsubscribe-auth/AXZ2Z5NL2IOUYZOVQWOPBT3U3RTGRANCNFSM5OTOMDFA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . You are receiving this because you authored the thread.Message ID: @.***>

What did you modify in the docker-compose to make the remote rcon work?

[mmmaxwwwell]

You have to expose the port under the ports section, I think it's 8080 iirc but I could be wrong

[Serenfo]

You have to expose the port under the ports section, I think it's 8080 iirc but I could be wrong

that exactly what i do but i'm lock on connecting on Vrage remote client :(

[DreamThief]

Same problem here, vrage client.
Using 8 character password, exposed the port in the docker-compose, changed the port incase of weird conflict (changed in client, cfg, and docker compose)

Everything is working perfectly except for the vrage connection, which means I cannot load mods.
Still working it, I'll post if I figure anything out.

[thelande]

Hi there! I recently discovered this repo when I was exploring options to run the SE dedicated server via Kubernetes. Thank you for putting this together; it saved me a ton of time and works well. I was also frustrated by the remote API not functioning so I decided to dig into the problem. I discovered two things during my digging:

1. To get the socket connection to the remote API to work, you either need to set the <RemoteApiIP> value in the config to the container's IP and then connect directly to that IP, or set the value to +, which in Wine translates to "any host". Either way, you must connect to the container's actual IP. Trying to connect to localhost or 127.0.0.1 on the container host won't work.
2. The remote API relies on a function in Wine, HttpSendResponseEntityBody, that is not implemented.

To get around (1) I added an NGINX reverse proxy that forwards all requests to the remote API by it's IP (config below). For (2), I implemented the function. My changes to the wine code base were just submitted so they will need to be reviewed and eventually merged before they make it into the wine packages. In the meantime, I am working on a custom Docker image that will contain my changes so folks can get started using them now. I need a couple more days to get that working, but will post here when it's ready.

This is the NGINX configuration (replace 172.17.0.2 with the container's actual IP):

# nginx.conf
server {
    listen 80;
    listen [::]:80;
    server_name localhost;

    location /vrageremote {
        proxy_pass http://172.17.0.2:8080;
    }
}

NGINX was run like so:

docker run -d --rm --name nginx-proxy \
  -v ./nginx.conf:/etc/nginx/conf.d/default.conf \
  -p 8080:80 nginx:stable