The Outbreak servers are open source.

[Isles487]

Thank you very much to all of you who have shared information here. I have been wanting to set up a server for a long time so that I can play with friends over the internet without having to use a VPN or anything too complicated

There is no need for a VPN to connect to our server and play. The only issue we sometimes see is that ISPs block DNS inquiries to our DNS server, and if that is the case, you simply set up using https://obsrv.org/wiki/index.php?n=Setu ... eDNSSetups.

-In the /etc/dnsmasq.d/obcomsrv file I have put my server internal IP (address=/gate1.jp.dnas.playstation.org/192.168.50.167 &
address=/www01.kddi-mmbb.jp/192.168.50.167)

This needs to be set as your public IP, not your internal IP.

-In the /etc/dnsmasq.conf file I have put my server internal IP: listen-address=192.168.50.167,127.0.0.1 and I deleted the # before the listen address.

I would revert to commenting this out, likely no need to define the listening address manually.

[DharmaCorp]

Thank you for your answer

I am aware of the servers on the forum and I have used them many times to play with my friends, but the problem is that we are from Spain, which adds some ping to the connection, and depending on the time, it becomes very difficult to play comfortably because enemies teleport around the map and some bosses are almost impossible to kill on high difficulty .
That's why I saw a good opportunity to avoid this problem and learn something.

I have modified the parameters you mentioned, but I still have the 6xx error on the DNAS. However, I no longer get the "closes connection" error.
What I have noticed, while looking at the log in /var/apache/logs/dnas_errors.log, is a message regarding SSL & HTTP/HTTPS:

Code: Select all

[Mon May 01 22:42:48.350351 2023] [ssl:info] [pid 764:tid 139990964299520] [client XXX.XXX.XXX.XXX:7600] AH01964: Connection to child 0 established (server gate1.jp.dnas.playstation.org:443) [Mon May 01 22:42:48.350483 2023] [ssl:info] [pid 764:tid 139990964299520] [client XXX.XXX.XXX.XXX:7600] AH01996: SSL handshake failed: HTTP spoken on HTTPS port; trying to send HTML error page [Mon May 01 22:42:48.350498 2023] [ssl:info] [pid 764:tid 139990964299520] SSL Library Error: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request -- speaking HTTP to HTTPS port!? [Mon May 01 22:42:48.448910 2023] [ssl:info] [pid 765:tid 139990964299520] [client XXX.XXX.XXX.XXX:7612] AH01964: Connection to child 64 established (server gate1.jp.dnas.playstation.org:443) [Mon May 01 22:42:48.449056 2023] [ssl:info] [pid 765:tid 139990964299520] [client XXX.XXX.XXX.XXX:7612] AH01996: SSL handshake failed: HTTP spoken on HTTPS port; trying to send HTML error page [Mon May 01 22:42:48.449073 2023] [ssl:info] [pid 765:tid 139990964299520] SSL Library Error: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request -- speaking HTTP to HTTPS port!?

[Isles487]

Thank you for your answer

I am aware of the servers on the forum and I have used them many times to play with my friends, but the problem is that we are from Spain, which adds some ping to the connection, and depending on the time, it becomes very difficult to play comfortably because enemies teleport around the map and some bosses are almost impossible to kill on high difficulty .
That's why I saw a good opportunity to avoid this problem and learn something.

I have modified the parameters you mentioned, but I still have the 6xx error on the DNAS. However, I no longer get the "closes connection" error.
What I have noticed, while looking at the log in /var/apache/logs/dnas_errors.log, is a message regarding SSL & HTTP/HTTPS:

Code: Select all

[Mon May 01 22:42:48.350351 2023] [ssl:info] [pid 764:tid 139990964299520] [client XXX.XXX.XXX.XXX:7600] AH01964: Connection to child 0 established (server gate1.jp.dnas.playstation.org:443) [Mon May 01 22:42:48.350483 2023] [ssl:info] [pid 764:tid 139990964299520] [client XXX.XXX.XXX.XXX:7600] AH01996: SSL handshake failed: HTTP spoken on HTTPS port; trying to send HTML error page [Mon May 01 22:42:48.350498 2023] [ssl:info] [pid 764:tid 139990964299520] SSL Library Error: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request -- speaking HTTP to HTTPS port!? [Mon May 01 22:42:48.448910 2023] [ssl:info] [pid 765:tid 139990964299520] [client XXX.XXX.XXX.XXX:7612] AH01964: Connection to child 64 established (server gate1.jp.dnas.playstation.org:443) [Mon May 01 22:42:48.449056 2023] [ssl:info] [pid 765:tid 139990964299520] [client XXX.XXX.XXX.XXX:7612] AH01996: SSL handshake failed: HTTP spoken on HTTPS port; trying to send HTML error page [Mon May 01 22:42:48.449073 2023] [ssl:info] [pid 765:tid 139990964299520] SSL Library Error: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request -- speaking HTTP to HTTPS port!?

Can you please post a picture of:

1) Your port forwarding rules
2) Following files: /etc/dnsmasq.d/obcomsrv
config.properties

[DharmaCorp]

Here the info:



/etc/dnsmasq.d/obcomsrv:

address=/gate1.jp.dnas.playstation.org/ISP ip
address=/www01.kddi-mmbb.jp/ISP ip

config.properties(is the same for ob1 and ob2):

# IP address for gameserver
gs_ip=ISP ip

# credentials for the database
db_user=bioserver
db_password=XXXXXXX

[Isles487]

Here the info:



/etc/dnsmasq.d/obcomsrv:

address=/gate1.jp.dnas.playstation.org/ISP ip
address=/www01.kddi-mmbb.jp/ISP ip

config.properties(is the same for ob1 and ob2):

# IP address for gameserver
gs_ip=ISP ip

# credentials for the database
db_user=bioserver
db_password=XXXXXXX

With the setup changed to the newer values, are you still able to connect to your server successfully from within your network?

What is the DNAS error number that users are receiving?

If your friends type in CMD prompt:

Code: Select all

nslookup gate1.jp.dnas.playstation.org your_public_ip

do they get the right response?

[DharmaCorp]

Sorry yesterday I didn't have time to check but I did the tests today and here the update:

are you still able to connect to your server successfully from within your network?

Yes, connection in LAN still ok.

I have tried doing an nslookup on both the private and public address locally, and both have responded correctly. However, when my friends try to do an nslookup pointing to the public IP, the address does not resolve

I have also tried checking if ports 53, 8300, etc. are open or not using https://www.yougetsignal.com/tools/open-ports/ and yes, open.

I still need to try in the PCSX2 configuration under the DNS section, if I could directly put the URL + public IP there and see if my friends can connect that way

[Isles487]

I have tried doing an nslookup on both the private and public address locally, and both have responded correctly. However, when my friends try to do an nslookup pointing to the public IP, the address does not resolve

I have also tried checking if ports 53, 8300, etc. are open or not using https://www.yougetsignal.com/tools/open-ports/ and yes, open.

I still need to try in the PCSX2 configuration under the DNS section, if I could directly put the URL + public IP there and see if my friends can connect that way

So, what might be happening is that your friends' routers or ISPs are not allowing DNS inquiries to certain DNS addresses, so they can't use your DNS server. There is a guide for setting DNS manually here: https://obsrv.org/wiki/index.php?n=Setu ... eDNSSetups. Your friends can use that and simply substitute your public IP address for all 3 of those values.

[DharmaCorp]

I have tried doing an nslookup on both the private and public address locally, and both have responded correctly. However, when my friends try to do an nslookup pointing to the public IP, the address does not resolve

I have also tried checking if ports 53, 8300, etc. are open or not using https://www.yougetsignal.com/tools/open-ports/ and yes, open.

I still need to try in the PCSX2 configuration under the DNS section, if I could directly put the URL + public IP there and see if my friends can connect that way

So, what might be happening is that your friends' routers or ISPs are not allowing DNS inquiries to certain DNS addresses, so they can't use your DNS server. There is a guide for setting DNS manually here: https://obsrv.org/wiki/index.php?n=Setu ... eDNSSetups. Your friends can use that and simply substitute your public IP address for all 3 of those values.

Yes, with that now they can connect!
So thanks a lot

[Isles487]

I have tried doing an nslookup on both the private and public address locally, and both have responded correctly. However, when my friends try to do an nslookup pointing to the public IP, the address does not resolve

I have also tried checking if ports 53, 8300, etc. are open or not using https://www.yougetsignal.com/tools/open-ports/ and yes, open.

I still need to try in the PCSX2 configuration under the DNS section, if I could directly put the URL + public IP there and see if my friends can connect that way

So, what might be happening is that your friends' routers or ISPs are not allowing DNS inquiries to certain DNS addresses, so they can't use your DNS server. There is a guide for setting DNS manually here: https://obsrv.org/wiki/index.php?n=Setu ... eDNSSetups. Your friends can use that and simply substitute your public IP address for all 3 of those values.

Yes, with that now they can connect!
So thanks a lot

Aaaay! Good to hear!

[hobbes_182]

Glad to hear you have started to host

The help on the forum is great, I'm the dumbest person I know, thanks to everyone on the thread I was able to get my server up and running too