Jump to content

Recommended Posts

Posted

Server running on dedicated hardware, port 10308 UDP is forwarded, public IP available, and proved to be working with HTTP, SRS and other servers.

 

The DCS is not visible on the clients list though, and choosing to connect directly results in "address unavailable" message, both with DDNS URL, and IP.

 

When VPN-tunneled to similar network (same ISP, same routing hardware with same configuration) - there is no such problems, and clients can see the server on the list, and connect directly to it.

[sIGPIC][/sIGPIC]

"If a place needs helicopters, it's probably not worth visiting." - Nick Lappos

  • 3 months later...
  • 11 months later...
Posted

i noticed it gives this error when server is full.

sometimes it gives me this error for no apparent reason , server not full and online, with people in.

sometimes i even have it on my own dedicated server…

 

any solution yet ?

  • 2 months later...
  • 3 weeks later...
Posted

Same ... all ports (10308 and 8088) forwarded to the dedicated server machine and TCP/UDP allowed. The server machine has had both ports opened, TCP/UDP also allowed. I can get it to work in MP from the local IP address but not when I try to connect via IP Connection button (public address) it always says "Address Unavailable" ... I've tried everything. I'm at a loss.

 

The last thing I have to try is change it from a wireless connection to a direct connection to the router via a CAT5 cable.

 

From the age of this message and the lack of a resolution I'm not very hopeful of a fix to this problem.

 

Shyte, thanks for any available help,

 

CTBlankenship

Intel I7-4770K @ 4.4GHz, 32GB RAM, EGVA GTX 1070 SC, Three ASUS PA248 24" monitors, 500 GB SSD, Saitek X-56 Throttle and Stick, TrackIR

  • 1 month later...
  • 3 weeks later...
Posted

i would like to suggest something that corrected an issue i was having (similar). join from the MP screen. and make sure the observer is not a name of someone trying to join. i had my game name in the spot and i could not join. i also saw the not available error too when i was trying to join by manipulating the IP to IPv4 (LAN and WAN) instead of IPv6. make sure you have IPv6 enabled and working.

  • Thanks 1

AKA_SilverDevil Join AKA Wardogs Email Address My YouTube

“The MIGS came up, the MIGS were aggressive, we tangled, they lost.”

- Robin Olds - An American fighter pilot. He was a triple ace.

The only man to ever record a confirmed kill while in glide mode.

Posted

First thought: have you tried using different ports? Change to 10408 or some such.

 

 

You might be coming across something similar to, or related to, this old thing.

❧ ❧ Inside you are two wolves. One cannot land; the other shoots friendlies. You are a Goon. ❧ ❧

  • 4 months later...
Posted (edited)

Evening fellow skymasters,

 

I am having the same issue, has there been a resolution yet ?

 

Regards

 

Edited by Epacseii
Update on logs
Posted (edited)
On 12/7/2020 at 10:08 PM, Flappie said:

Hi Epacseii. Please attach a DCS log showing the issue ( C:\Users\username\Saved Games\DCS...\Logs\dcs.log and dcs.log.old).

 

Forgot you probably looking for the the server Logs... 😕

 

Edited by Epacseii
Posted

Both your IPv4 and IPv6 interfaces are up. That's a good start.

 

2020-12-07 20:14:35.607 INFO    NET: server has started
2020-12-07 20:14:35.609 INFO    NET: Using LEDBAT for UDP congestion control.
2020-12-07 20:14:39.630 INFO    NET: No UPNP devices found.
2020-12-07 20:14:39.630 INFO    NET: Successfully set up Dual-Stack socket, using both IPv4 and IPv6
2020-12-07 20:14:39.630 INFO    NET: Listen to IPv6 on port 10308

 

I see you're running default 10308 port. Have you tried what Tippis suggested above, using a different TCP/UDP port?

---

Posted (edited)
14 hours ago, Flappie said:

Both your IPv4 and IPv6 interfaces are up. That's a good start.

 



2020-12-07 20:14:35.607 INFO    NET: server has started
2020-12-07 20:14:35.609 INFO    NET: Using LEDBAT for UDP congestion control.
2020-12-07 20:14:39.630 INFO    NET: No UPNP devices found.
2020-12-07 20:14:39.630 INFO    NET: Successfully set up Dual-Stack socket, using both IPv4 and IPv6
2020-12-07 20:14:39.630 INFO    NET: Listen to IPv6 on port 10308

 

I see you're running default 10308 port. Have you tried what Tippis suggested above, using a different TCP/UDP port?

 

Tried using port 10408 still no results, however if I host within my network it picks it up, similarly with 10308, so that rules out any server issues... please advise what else can be done ? On the DCS server tracker is shows the server but shows it is offline... wondering why ?

DCStrack.png

Edited by Epacseii
Posted (edited)
13 hours ago, Flappie said:

Does your 10408 port shows up online here? https://www.canyouseeme.org/

 

Yes thank you, I have seem to have found the problem. I was not running DCS world steam version of open beta. When I ran the beta version on steam, it found the game in the lobby and we can join. Thanks for the assistance! In short: If you run DCS open beta server, make sure you are running DCS world beta version.

 

https://steamcommunity.com/app/223750/discussions/0/1735468061762962880/

 

 

Edited by Epacseii
  • 1 month later...
Posted

Was anyone else able to find a solution here? I'm running into the same problem. Connection is fine on the local network. Verified port 10308 is visible from the internet and forwarded correctly.

  • 9 months later...
Posted

I run into this problem no matter what I do. Running a dedicated open beta server from desktop works fine, but when I try to start one from my server, it will not list in-game, and mostly will not be accessible from outside my network.

I've tried running in a VM inside Truenas, a VM inside TrueNAS running on Proxmox and now a instance running on Debian with Wine, inside a LXC container in Proxmox, all with the same result. I've checked and double-checked ports in router, checked versions, opened ports in Iptables, disabled proxmox firewall, tried different ports, tried different DCS acounts - nothing helps.

Looking at the log file I see "ConflictInMappingEntry" fails for both ports 10308 and 8088, but I cannot analyze the significance of this.

dcs.log

  • 3 weeks later...
  • 3 weeks later...
Posted

I don't know 🙂

In the end, I reinstalled my virual machine and redid it following this instructional:

 

It's sort of the same as I've done things before, but with the debloating and diabling of unused network features in windows. Now it works! And I'm not changing anything ever again 😃

  • Thanks 1
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...