[DiscordArchive] Are bnet+worldserver running? Locally or on a different machine?
[DiscordArchive] Are bnet+worldserver running? Locally or on a different machine?
Original source
Are bnet+worldserver running? Locally or on a different machine?
rektbyfaith
09-22-2025, 06:13 AM #1Archived author: ModoX • Posted: 2025-09-22T06:13:51.535000+00:00
Original source
Are bnet+worldserver running? Locally or on a different machine?
Original source
If its a different machine: make sure you adjust LoginREST in bnetserver config, create portforward on fws towards the server.
Also make sure to use arctium launcher to run wow
rektbyfaith
09-22-2025, 06:15 AM #2Archived author: ModoX • Posted: 2025-09-22T06:15:04.232000+00:00
Original source
If its a different machine: make sure you adjust LoginREST in bnetserver config, create portforward on fws towards the server.
Also make sure to use arctium launcher to run wow
Original source
So yeah, LoginREST is my public ipv4 for the dedicated server, so they're a different machine. They are running yeah, the realm shows up in bnetserver. Could it be the certificate issue? I had to use my SSL cert I generated for the domain so I can hide the IP a little bit.
~~When you say port fowrard, using Windows it's the Inbound rules, right? So I need ports 1119, 8081, 8085, 8086 correct?~~
So I just double checked, the ports are working fine and I relaunched the bnet+world to make sure, instant BLZ51914003 error after entering password. No idea what's causing it.
I am also using the Arctium Launcher if it helps.
rektbyfaith
09-22-2025, 06:18 AM #3Archived author: Clerk • Posted: 2025-09-22T06:18:32.173000+00:00
Original source
So yeah, LoginREST is my public ipv4 for the dedicated server, so they're a different machine. They are running yeah, the realm shows up in bnetserver. Could it be the certificate issue? I had to use my SSL cert I generated for the domain so I can hide the IP a little bit.
~~When you say port fowrard, using Windows it's the Inbound rules, right? So I need ports 1119, 8081, 8085, 8086 correct?~~
So I just double checked, the ports are working fine and I relaunched the bnet+world to make sure, instant BLZ51914003 error after entering password. No idea what's causing it.
I am also using the Arctium Launcher if it helps.
Original source
I hope I explained that well enough
rektbyfaith
09-22-2025, 06:20 AM #4Archived author: Clerk • Posted: 2025-09-22T06:20:43.746000+00:00
Original source
I hope I explained that well enough
Original source
Reverse proxying via cloudflare may break it. I recall situations where that was a problem. A cert is mandatory
rektbyfaith
09-22-2025, 06:35 AM #5Archived author: ModoX • Posted: 2025-09-22T06:35:14.078000+00:00
Original source
Reverse proxying via cloudflare may break it. I recall situations where that was a problem. A cert is mandatory
Original source
So I do have proxy off for the particular subdomain during the time I tried logging in.
rektbyfaith
09-22-2025, 06:35 AM #6Archived author: Clerk • Posted: 2025-09-22T06:35:58.560000+00:00
Original source
So I do have proxy off for the particular subdomain during the time I tried logging in.
Original source
Portchecker shows them all except 8086 open but it's been added as an inbound rule the same way and a legion core was working before 11.2 so idk.
rektbyfaith
09-22-2025, 06:48 AM #7Archived author: Clerk • Posted: 2025-09-22T06:48:34.569000+00:00
Original source
Portchecker shows them all except 8086 open but it's been added as an inbound rule the same way and a legion core was working before 11.2 so idk.
Original source
If it helps ```[176.65.149.45:43044] SSL Handshake failed http request (SSL routines)``` has just popped up in the bnetserver console. (Sorry for the ping)
rektbyfaith
09-22-2025, 07:02 AM #8Archived author: Clerk • Posted: 2025-09-22T07:02:38.824000+00:00
Original source
If it helps ```[176.65.149.45:43044] SSL Handshake failed http request (SSL routines)``` has just popped up in the bnetserver console. (Sorry for the ping)
Original source
loginrest config must be a domain name, not raw ip.for external host
rektbyfaith
09-22-2025, 07:08 AM #9Archived author: Tea • Posted: 2025-09-22T07:08:02.252000+00:00
Original source
loginrest config must be a domain name, not raw ip.for external host
1 Guest(s)
1 Guest(s)