Fixed Internally Patcher problems

Firstly, I can not say for sure that this is not something on my end, that said, I have not changed or updated anything on my end since this started happening the last week.

I have started getting 4-503 errors when I launch the patcher. Once it starts on a machine, it is basically impossible to get the patcher to launch as it should. Even with following all the tricks of deleting cache and so on. If I use the patchme trick with the eqgame.exe file, the game launches just fine and I can play. I have my box's on separate physical hardware and separate internal IP's but as with most ISP's, I only have one external IP.

It seems to be spreading to the other computers, so I am wondering:

1) Did my IP/mac-addresses some how get caught in your anti DDOS script/filter since I am running a few box's?
2) Did you make any other changes last week that could account for this?

The odd thing is, once a box has started to get the 4-503 error, it seems to be blocked from contacting the patch server "permanently".....

My other box's that have not yet gotten the 4-503 error, works just fine.

PS: Could you add a refresh/retry button to the launcher, so that you don't have to restart the entire thing every time something like this happens?

Update: If you are having the problem that is reported in this thread the fix seems to be:

Have you googled 4-503 error? Get a bunch of daybreak games links, tho seems many were not for EQ they may still help.

Yes, I have googled it and followed the link that the patcher gives to the help article, non of the suggestions helped, that is why I am wondering if this is something "new". Ergo the question if they changed their DDOS script/rules, it could cause something like this, since I know our DDOS systems could behave like this under the right circumstances.

I, too, am having this problem. Some time last week one of my computers had this happen, where I get the LaunchPad was unable to connect 4-503 error when trying to launch EQ. Even after trying to follow all the steps, I was not able to get that computer to connect to the Launcher. So, I reimaged the computer, reinstalled EQ and everything, and was able to connect.... once. Now, I am again getting the 4-503 error on it as well as one of my other computers.

So... what I can see from this post is that issue is happening to multiple people and doesn't seem to be specific to an individual computer. Any chance we could get someone to look into the issue, please?

Also seeing this issue.
Have tried all the suggested 'fixes' with no luck.
Have attempted a clean install but this fails since the patcher will not connect.

This issue is also effecting EQ2.

This issue started for me on Saturday. Logged into first account with no issues. Tried to log in second account and got 'unable to connect'. Only way I can play at the moment is by using the 'patchme' fix. Tried to do a new install but still got the same error. This is kind of worrying as there is a patch this week.

Also happens with EQ2 and no one seems to answer if it is possible to patch without using launchpad.

Just started for me yesterday. If I s/d computer completely it works once. I can load the game using the patchme setting on eqgame.exe just fine when this happens. Not sure whats going on, its one of my 5 computers, laptop. others are fine.
Must have got lucky on the s/d the first time, just s/d and restarted and got same error.

Have tried some of the fixes on this site, deleting some patcher config files, resetting modem, deleting patcher folder in eq and reinstalling. Keep having same issue, LaunchPad was unable to connect. (4-503) code. Patchme lets me log in to game bypassing launcher but not sure how that will work come tomorrow. Its only one machine out of five doing this, all others are connected to router through a switch via wired connection as is this machine.

Log info from end of success to failure to launch
2022-07-1910:24:38165824067328144330527388Displaying Loading screen, url=file:///LaunchPad.libs/Web/loading.html.
2022-07-1910:24:38165824067328244330527403Destroying basic splash screen.
2022-07-1910:24:38165824067329244330527540Received ready event from the view. view=Loading
2022-07-1910:24:42165824067329344330532179reloading main screen, url=https://lpj.daybreakgames.com/eq/live/?t=43305&tPartyCmdLine=patchme
2022-07-1910:24:46165824067333544330535546Failed to load the main view.
2022-07-1910:24:46165824067333714330535559Fatal error occurred, errorCode=4.
2022-07-1910:24:46165824067333844330535561[GameLauncherClient] State transition request to DisplayingRecoveryScreen.
2022-07-1910:24:46165824067333944330535583TransitionState - oldState=LoadingMainScreen, newState=DisplayingRecoveryScreen, totalTimeInStateMs=8481.
2022-07-1910:24:46165824067334044330535593[GameLauncherClient, DisplayingRecoveryScreen] State - OnEnter(Begin)
2022-07-1910:24:46165824067334444330535627Loading the recovery screen, url=local:error-connection.html
2022-07-1910:24:46165824067336744330535926LoadUrl - loading site, url=local:error-connection.html, viewName=Recovery.
2022-07-1910:24:46165824067336944330535940[GameLauncherClient, DisplayingRecoveryScreen] State - OnEnter(End), totalTimeMs=347.
2022-07-1910:24:46165824067337944330536243OnLoadViewSite - url=, viewName=Recovery, pageLoadTime=317 ms, loadResult=Success.
2022-07-1910:24:46165824067338044330536244Displaying Recovery screen, url=file:///LaunchPad.libs/Web/error-connection.html.
2022-07-1910:24:47165824067338144330536263Destroying basic splash screen.
2022-07-1910:24:47165824067338644330536328Received ready event from the view, ignoring.
2022-07-1910:25:51165824067346144330600982Engine viewport closed by user, will request shutdown.
2022-07-1910:25:51165824067346244330600983RequestShutdown - Shutdown requested, reason=UserExit.
2022-07-1910:25:51165824067346444330601016[GameLauncherClient] Stopping state machine.
2022-07-1910:25:51165824067346544330601028GameLauncherClient - state machine finished.
2022-07-1910:25:51165824067347444330601132Run - ending the run.
2022-07-1910:25:51165824067347544330601133Shutting down.
2022-07-1910:25:51165824067347644330601145ProcessSyncEvent GameIsReady destroyed.
2022-07-1910:25:51165824067347744330601158Destroying the http manager.
2022-07-1910:25:51165824067347844330601171Destroying the application updater api.
2022-07-1910:25:52165824067347944330601184Disabling command processing.
2022-07-1910:25:52165824067348044330601198Shutting down browser patcher.
2022-07-1910:25:52165824067348144330601212Destroying the browser patcher.
2022-07-1910:25:52165824067348244330601225Destroying the native patcher.
2022-07-1910:25:52165824067348344330601239Destroying patcher object factory.
2022-07-1910:25:52165824067348444330601253Destroying auxiliary views.
2022-07-1910:25:52165824067348544330601267Destroying basic splash screen.
2022-07-1910:25:52165824067348844330601286Shutting down engine.
2022-07-1910:25:52165824067349044330601310Destroying main view.
2022-07-1910:25:52165824067349344330601356Shutting down cef.
2022-07-1910:25:52165824067349444330601437Shutting down log service.

This worked for me, posted by Tarvas in Player support in this thread.
https://forums.daybreakgames.com/eq...es-cant-get-more-than-2-characters-in.284330/
Doesnt fix the issue permanently, but will let me log in through patcher. Have had to redo the fix each time I start game.

This is now happening to all four of my computers that are on the same network switch. I am able to get into the game using the patchme workaround, though.

I have been boxing with my current set up for a couple years with no issues with the launcher. This past few days I first got the (4-503) error on one laptop, then a couple days later a second, then today it seems to be about four of my machines.

With the launcher window open with the error in the center white box, I then hit Control + Shift + Esc to bring up the task manager. I select the Daybreak games launcher in the top app window and right click -> then Expand. This shows x3 "GameLauncherCefChildProcess.exe" processes running. I click on the top one and end the process. This instantly pushes the error window in the launcher to a normal successful load with the Play button.

No idea what is causing this, hopefully it is something that's in the works for a fix, as it seems many people are experiencing the problem.

I had this happening on one machine and today it started on a second one. The second one only had it happen twice though, then it loaded fine. same errors

Not sure if this is relevant or not, but I just noticed that this is just happening on my box's that are a few years old and running Intel processors, my box's that I bought this year that are running AMD is not effected.

Has anyone seen this bug on a machine running an AMD processor or is this error only happening on Intel machines?

It happens on my Lenovo laptop, AMD A4-7210 and AMD Radeon R3 graphics chip. Windows 10 home, ver 21H2. Consistently happening on this machine, no other way to get online using the patcher without using Taskmanage to closeout child processes of the launcher until the launcher loads. Have had a single child process and up to 3 at a time. I have to go down the line ending the task until finally the patcher loads all the way.

So it is an older processor (2015), like my Intel box's that are having problems. The box's that have CPU's from 2021 (AMD) have no problems, the one's with CPU's that are older (Intel CPU's), are having problems though.

List of CPU's with problems with the patcher and without:

CPU's with problems:
Intel Celeron N3450 (2016)
AMD A4-7210 (2015)
Intel Celeron J3455 (2016)

CPU's without the problem
AMD Ryzen 9 5950X (2020)
AMD Ryzen 7 4700U (2020)
AMD Ryzen 5 4500U (2020)
AMD Ryzen 5 3600 (2019)

Big same. Not sure what's going on. Has been happening intermittently on 1 of my desktops, and 1 of my laptops...

What CPU's do your comps have?