Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
https://docs.google.com/document/d/e/2PACX-1vTk67puClDitrjLeAT3NrkgGQAUD2ZWSgVkj_NUAbmT-rBa4Tejx4uY7_-4Gpn_swNKIMjoS-g7255O/pub
For multiple servers, you will need JUST ONE CUSTOMER KEY and 1 PROVIDER KEY for each server. So if you want host 3 oasis, you will need 1 customer key and 3 provider keys.
And you will need open:
- 2 ports for each server and 1 query port for each server too.
You can create your CustomerKey and all others ProviderKeys you want and set up your oasis here:
https://myrealm.lastoasis.gg/
You can get your external-ip (IPv4) here:
https://www.whatismyip.com/
If you do not have dedicated ip adress you must change the ip on all bats before start the servers.
So if u want 3 server, you will need something like this:
- Server 1:
Port: 50000 and 50001
Query Port: 27015
- Server 2:
Port: 50002 and 50003
Query Port: 27016
- Server 3:
Port: 50004 and 50005
Query Port: 27017
Create one bat file to launch each server:
Server 1:
Server 2:
Server 3:
You have to allow all ports with firewall rules and make the ports forward at your routers config.
So, to start you server, of course you need already create all oasis at Real's website and run the 3 bat files to start your servers.
I made one app that create all firewall rules and generate you the code to the bats that will start your server. But you still need do the port forwards manually.
Video showing how it works and download link:
https://streamable.com/qul2fb
We can access one oasis (the active one) in Single Oasis mode and can switch between oases, but if we change to Multiple we lose access to the one that was active and are denied access to the additional ones.
The only thing I can see different in our batch files are the spaces you added to: "backend.last - oasis.com" and the port numbers I am using.
I have watched your video but cannot check thing in Defender as I am running Norton. But the fact we can talk to MyRealm at one level would indicate all the port forwarding is working OK.
BTW, my friend is having exactly the same issues.
If you go to your Realms dash board, do you saw all your servers running?
Like this pic:
https://prnt.sc/1n09wxi
The ports you can use are the ones you want. You have just to make sure you set 2 ports for port: E.g. Your first port is 5555 so the port for your second server is 5555 + 2, that means: 5557 the 3rd is: 5559 and goes on.
As you are using norton you have to set all your ports to Norton's firewall instead windows firewall. All ports both TCP and UDP protocols and both inbound and outbound rules.
You can verify if norton is the problem or not: Disable Norton AND Windows Firewall (normally after you disable a 3rd party anti virus/firewall, defender/windows automatically enables, so make sure you go to windows defender and disable anti virus and firewall too.
Check if you can travel to another server/oasis.
If you can, for sure Norton/Firewall is your problem.
But still you have to do port forward too if your router has an internal firewall.
Most of the routers has and it comes enabled by default.
So you must add the ports and forward all of then too.
If your router has DMZ option, you can enable DMZ and set there your INTERNAL IP.
So this way you do not have to worry about port forwards. But it is too risky, i do not recommend for live servers. Just for tests purposes.
Make sure the .BAT have your EXTERNAL IP and:
1- Press Windows Key + X and open: Windows PowerShell (Admin)
2- Paste the command below and press RETURN:
I do not tested, but maybe it can fix your problem.
Yes this will prolly fix issues with local connect to your server, however, it WILL cause problems with anything else that uses localhost, and you do not need to restart your cpu for changes to take effect.
But it will probably fix connection issues you are having, so is valid info
Glad u can enjoy now!!!
i've looked through the logs and it has some errors that the standard does too, it connects to steam then shuts itself down for some reason, yet if i switch back from classic, it launches to server ready