Hello
Thx - I posted the Logfile in a new thread like recommended.
Latest posts made by BadJohN
-
RE: login issue
-
Login Screen and nothing more...
Hello!
Lika a lot of other people I got the Login screen and nothing further.
I have the same problem with login since the update to the new version v2021.11.0.
I did the following...I deinstalled my Antivirus
I completely reset my Windows network
I flushed my DND
I reset my router
I turned off my firewall completely
I installed older versions of FAF, but it says "Your version is outdatet- you need to update to a new version"
I deinstalled and Installed FAF like 20 times between these steps.Still the always the same error..
Anyone any ideas?
see Logfile Data..Greetings
JohnLOG Data:
2021-12-06 15:52:09.761 INFO 3988 --- [JavaFX-Launcher] o.s.boot.SpringApplication : Starting application using Java 15.0.1 on %CPU_NAME% with PID 3988 (started by %USER% in C:\GAMES\FAF Client)
2021-12-06 15:52:09.763 INFO 3988 --- [JavaFX-Launcher] o.s.boot.SpringApplication : The following profiles are active: windows,prod
2021-12-06 15:52:10.453 INFO 3988 --- [JavaFX-Launcher] trationDelegate$BeanPostProcessorChecker : Bean 'faf-client-com.faforever.client.config.ClientProperties' of type [com.faforever.client.config.ClientProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2021-12-06 15:52:10.455 INFO 3988 --- [JavaFX-Launcher] trationDelegate$BeanPostProcessorChecker : Bean 'fafClientApplication' of type [com.faforever.client.FafClientApplication$$EnhancerBySpringCGLIB$$310c617] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2021-12-06 15:52:10.467 INFO 3988 --- [JavaFX-Launcher] trationDelegate$BeanPostProcessorChecker : Bean 'platformService' of type [com.faforever.client.fx.PlatformService] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2021-12-06 15:52:10.468 INFO 3988 --- [JavaFX-Launcher] trationDelegate$BeanPostProcessorChecker : Bean 'reportingService' of type [com.faforever.client.reporting.ReportingService] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2021-12-06 15:52:10.471 INFO 3988 --- [JavaFX-Launcher] trationDelegate$BeanPostProcessorChecker : Bean 'baseConfig' of type [com.faforever.client.config.BaseConfig$$EnhancerBySpringCGLIB$$31a93234] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2021-12-06 15:52:10.475 INFO 3988 --- [JavaFX-Launcher] trationDelegate$BeanPostProcessorChecker : Bean 'messageSource' of type [org.springframework.context.support.ReloadableResourceBundleMessageSource] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2021-12-06 15:52:10.577 INFO 3988 --- [JavaFX-Launcher] c.f.c.preferences.PreferencesService : Switching FA Forever logging configuration to INFO
2021-12-06 15:52:10.578 INFO 3988 --- [JavaFX-Launcher] trationDelegate$BeanPostProcessorChecker : Bean 'preferencesService' of type [com.faforever.client.preferences.PreferencesService] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2021-12-06 15:52:10.579 INFO 3988 --- [JavaFX-Launcher] trationDelegate$BeanPostProcessorChecker : Bean 'i18n' of type [com.faforever.client.i18n.I18n] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2021-12-06 15:52:10.580 INFO 3988 --- [JavaFX-Launcher] trationDelegate$BeanPostProcessorChecker : Bean 'notificationService' of type [com.faforever.client.notification.NotificationService] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2021-12-06 15:52:10.581 INFO 3988 --- [JavaFX-Launcher] trationDelegate$BeanPostProcessorChecker : Bean 'asyncConfig' of type [com.faforever.client.config.AsyncConfig$$EnhancerBySpringCGLIB$$168c594f] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2021-12-06 15:52:10.594 INFO 3988 --- [JavaFX-Launcher] trationDelegate$BeanPostProcessorChecker : Bean 'cacheConfig' of type [com.faforever.client.config.CacheConfig$$EnhancerBySpringCGLIB$$77cb0c95] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2021-12-06 15:52:11.074 INFO 3988 --- [JavaFX-Launcher] c.f.c.map.generator.MapGeneratorService : Deleting leftover generated maps...
2021-12-06 15:52:11.175 INFO 3988 --- [JavaFX-Launcher] com.faforever.client.update.Version : The current application version is: 2021.11.0
2021-12-06 15:52:11.176 INFO 3988 --- [JavaFX-Launcher] c.f.client.update.ClientUpdateService : Current version: 2021.11.0
2021-12-06 15:52:11.182 INFO 3988 --- [pool-3-thread-3] c.f.client.update.CheckForUpdateTask : Checking for client update
2021-12-06 15:52:11.187 INFO 3988 --- [pool-3-thread-4] c.f.c.update.CheckForBetaUpdateTask : Checking for client update (pre-release channel)
2021-12-06 15:52:11.484 INFO 3988 --- [JavaFX-Launcher] o.s.boot.SpringApplication : Started application in 2.287 seconds (JVM running for 3.24)
2021-12-06 15:52:12.595 INFO 3988 --- [JavaFX Application Thread] com.faforever.client.update.Version : fromVersion '1.5' is not newer than toVersion '2021.11'. No update is required.
2021-12-06 15:52:12.630 INFO 3988 --- [JavaFX Application Thread] com.faforever.client.user.UserService : Logging in with refresh token
2021-12-06 15:52:18.080 ERROR 3988 --- [reactor-tcp-nio-1] com.faforever.commons.lobby.FafLobbyApi : Could not connect to %CPU_NAME%java.net.UnknownHostException: failed to resolve 'lobby.faforever.com' after 3 queries
at io.netty.resolver.dns.DnsResolveContext.finishResolve(DnsResolveContext.java:1046)
at io.netty.resolver.dns.DnsResolveContext.tryToFinishResolve(DnsResolveContext.java:999)
at io.netty.resolver.dns.DnsResolveContext.query(DnsResolveContext.java:417)
at io.netty.resolver.dns.DnsResolveContext.access$600(DnsResolveContext.java:65)
at io.netty.resolver.dns.DnsResolveContext$2.operationComplete(DnsResolveContext.java:466)
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:578)
at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:571)
at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:550)
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:491)
at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:616)
at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:609)
at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:117)
at io.netty.resolver.dns.DnsQueryContext.tryFailure(DnsQueryContext.java:224)
at io.netty.resolver.dns.DnsQueryContext$4.run(DnsQueryContext.java:176)
at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:469)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:832)
Caused by: io.netty.resolver.dns.DnsNameResolverTimeoutException: [/192.168.0.1:53] query via UDP timed out after 5000 milliseconds (no stack trace available)2021-12-06 15:52:18.081 ERROR 3988 --- [reactor-tcp-nio-1] com.faforever.commons.lobby.FafLobbyApi : Error during connection
java.net.UnknownHostException: failed to resolve 'lobby.faforever.com' after 3 queries
at io.netty.resolver.dns.DnsResolveContext.finishResolve(DnsResolveContext.java:1046)
at io.netty.resolver.dns.DnsResolveContext.tryToFinishResolve(DnsResolveContext.java:999)
at io.netty.resolver.dns.DnsResolveContext.query(DnsResolveContext.java:417)
at io.netty.resolver.dns.DnsResolveContext.access$600(DnsResolveContext.java:65)
at io.netty.resolver.dns.DnsResolveContext$2.operationComplete(DnsResolveContext.java:466)
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:578)
at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:571)
at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:550)
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:491)
at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:616)
at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:609)
at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:117)
at io.netty.resolver.dns.DnsQueryContext.tryFailure(DnsQueryContext.java:224)
at io.netty.resolver.dns.DnsQueryContext$4.run(DnsQueryContext.java:176)
at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:469)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:832)
Caused by: io.netty.resolver.dns.DnsNameResolverTimeoutException: [/192.168.0.1:53] query via UDP timed out after 5000 milliseconds (no stack trace available)2021-12-06 15:53:02.349 WARN 3988 --- [JavaFX Application Thread] c.f.client.fa.relay.ice.IceAdapterImpl : Ignoring call to ICE adapter as we are not connected: quit([])
2021-12-06 15:53:02.351 INFO 3988 --- [JavaFX Application Thread] c.f.client.remote.Faf%CPU_NAME%Accessor : Closing lobby %CPU_NAME% connection
2021-12-06 15:53:02.351 WARN 3988 --- [JavaFX Application Thread] com.faforever.commons.lobby.FafLobbyApi : Attempting to disconnect while never connected
2021-12-06 15:53:04.383 INFO 3988 --- [JavaFX Application Thread] com.faforever.client.config.AsyncConfig : Shutting down ExecutorService 'taskExecutor' -
RE: login issue
Hello!
I have the same problem with loging in with the new version since 2021.11.0.
I did the following...I deinstalled my Antivirus
I completely reset my Windows network
I flushed my DNS
I reset my router
I turned off my firewall completely
I installed older versions of FAF, but it says "Your version is outdatet- you need to update to a new version"
I deinstalled and Installed FAF like 20 times between these steps.Still the same error..
Anyone any ideas?Greetings
John -
RE: connection probleme
Unfortunately there are many problems with the new version..
There are many people with he same issue like me and you.
Hopefully they can fix this error soon -
RE: Stuck in the FAF Loggin with the loading buffer
Unfortunately, I have the same issue..
Tryied the new https://github.com/FAForever/downlords-faf-client/releases/tag/v2021.11.0-alpha4 with the same result..
Stuck at login screen.I have the same problem with loging in with the new version since 2021.11.0.
I did the following...I deinstalled my Antivirus
I completely reset my Windows network
I flushed my DNS
I reset my router
I turned off my firewall completely
I installed older versions of FAF, but it says "Your version is outdatet- you need to update to a new version"
I deinstalled and Installed FAF like 20 times between these steps.Still the same error..
Anyone any ideas?Greetings
John -
RE: Log in Issue
Hello!
After I upgraded to the new version 2021.0.11 I have the same problem - before everything was okay and I could log in without any problems.
I hope you can fix that bug soon- Thanks!
Greetings
JohnP.S.: If you still do need more logfiles please contact me- no problem
-
RE: Wont load beyond logging in screen
Hello!
After I upgraded to the new version 2021.0.11 I have the same problem - before everything was okay and I could log in without any problems.
I hope you can fix that bug soon- Thanks!
Greetings
JohnP.S.: If you still do need moreclient.log logfiles please contact me- no problem!