Nelinski

Fixed it, it's always the simplest things. I had a trailing / at the end of the home server URL in the compose file. Removed that and it starts fine.

@tekolote Thanks, that was helpful. I think I've made progress but still not 100% there. When I go to my sliding URL/.well-known/matrix/client I get the return as expected: {"m.homeserver": {"base_url": "https://bridge.domain.co.uk"}, "org.matrix.msc3575.proxy": {"url": "https://sliding.domain.co.uk"}} If I go directly to https://sliding.domain.co.uk I get a 404 error. When configuring Element X, I enter the URL as https://sliding.domain.co.uk and it detects I've got sliding enabled but doesn't get past that first configuration screen. Looking at the sliding logs it has the following: 21:14:48 INF Received connection from unknown access token, querying with homeserver 21:14:48 INF c= duration=0.000 path=//_matrix/client/r0/account/whoami size=0 status=301 21:14:48 INF c= duration=0.000 path=/_matrix/client/r0/account/whoami size=19 status=404 {"level":"warn","error":"/whoami returned HTTP 404","time":"2024-03-23T21:14:48Z","message":"failed to get user ID from device ID"} 21:14:48 ERR failed to get or create Conn error="HTTP 502 : /whoami returned HTTP 404" Any ideas? ( @JEZBRO if you're able to help too, appreciate the offer!)

@JEZBRO I'm trying to set this up but with SWAG. I believe I've followed this all to a T but I'm getting a 403. Any suggestions of what to check/look for to get this working?

@dbh It's this variable when you edit the docker template - NAME_SERVERS. Just remove all the other IP addresses listed (e.g. the DNS servers listed) and put "8.8.8.8,8.8.4.4".

I've updated my name servers/dns for the docker just to "8.8.8.8,8.8.4.4" and it fixed the issue. This was recommended in another thread somewhere (can't recall where). Works fine for me ever since.

If you don't delete your app data it will be.

Same here. A bit strange as the docker hub still shows the latest tag as valid and was last updated recently.

+1 for this please!

I've just had this issue too now.

Docker runs fine for me, I've actually got two running simultaneously and they're both fine. I also get that warning in my logs but the docker works fine even with that warning: 0030:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (00000000010CF4E0 1 C) semi-stub I had the exact same behaviour until I correctly port forwarded. I could see my lobby but couldn't connect to it: How many cores have you assigned to the ACC Server docker? If you left it all night and it finally got past that point, it sounds like you haven't got much power and it's taking a while to run. I had to assign more cores to the docker as mine all default to 1 core. Post a screenshot of your docker edit page (advanced mode) and share your ACC config files here and I'll double check them @hackspy679

No problem, appreciate you looking into it anyway! If I can test at all, do let me know.

Yeah I have a feeling you need to own the game in order to download the server but the server is a separate download via steam so you don't have to install the main game too.

Is there a way to auto update the Assetto Corsa Competizione server (accserver.exe) you have to manually include? There have been quite a few updates to it recently so it means my server is always out of date.

All working for me too now, thanks!