FAForever Forums
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Login

    Can't connect to FAF #2 (as requested)

    Scheduled Pinned Locked Moved
    I need help
    6
    8
    772
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K
      kandaker
      last edited by

      Creating a new thread for the continuation of FAF client login issues, as requested by @magge on thread #1.

      Here's a snapshot of what my client keeps logging in the log files as the UI keeps spinning on "logging in". I've tried starting the client offline. I tried starting with a fresh client.prefs file. Not sure what else to try...
      2023-10-08T09:39:30.223-07:00 DEBUG 14064 --- [reactor-tcp-nio-2] c.faforever.commons.lobby.FafLobbyApi : Starting session listener
      2023-10-08T09:39:30.224-07:00 INFO 14064 --- [reactor-tcp-nio-2] c.faforever.commons.lobby.FafLobbyApi : Connected to lobby.faforever.com on port 8002
      2023-10-08T09:39:30.397-07:00 ERROR 14064 --- [reactor-tcp-nio-2] c.faforever.commons.lobby.FafLobbyApi : Inbound channel closed with error

      java.net.SocketException: Connection reset
      at java.base/sun.nio.ch.SocketChannelImpl.throwConnectionReset(SocketChannelImpl.java:394)
      at java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:426)
      at io.netty.buffer.UnpooledDirectByteBuf.setBytes(UnpooledDirectByteBuf.java:570)
      at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132)
      at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:357)
      at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:151)
      at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788)
      at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
      at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
      at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
      at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
      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:833)

      2023-10-08T09:39:30.398-07:00 INFO 14064 --- [reactor-tcp-nio-2] c.faforever.commons.lobby.FafLobbyApi : Inbound channel cancelled
      2023-10-08T09:39:30.398-07:00 INFO 14064 --- [reactor-tcp-nio-2] c.faforever.commons.lobby.FafLobbyApi : Outbound channel cancelled
      2023-10-08T09:39:30.399-07:00 INFO 14064 --- [reactor-tcp-nio-2] c.faforever.commons.lobby.FafLobbyApi : Disconnected from server
      2023-10-08T09:39:30.399-07:00 INFO 14064 --- [reactor-tcp-nio-2] c.faforever.commons.lobby.FafLobbyApi : Attempting to reconnect
      2023-10-08T09:39:30.399-07:00 INFO 14064 --- [reactor-tcp-nio-2] c.faforever.commons.lobby.FafLobbyApi : Disconnected from server
      2023-10-08T09:39:30.400-07:00 INFO 14064 --- [reactor-tcp-nio-2] c.faforever.commons.lobby.FafLobbyApi : Attempting to reconnect
      2023-10-08T09:40:30.224-07:00 WARN 14064 --- [parallel-4] c.faforever.commons.lobby.FafLobbyApi : Could not reach server retrying: Attempt #1 of 10

      java.util.concurrent.TimeoutException: Did not observe any item or terminal signal within 60000ms in 'flatMap' (and no fallback has been configured)
      at reactor.core.publisher.FluxTimeout$TimeoutMainSubscriber.handleTimeout(FluxTimeout.java:295)
      at reactor.core.publisher.FluxTimeout$TimeoutMainSubscriber.doTimeout(FluxTimeout.java:280)
      at reactor.core.publisher.FluxTimeout$TimeoutTimeoutSubscriber.onNext(FluxTimeout.java:419)
      at reactor.core.publisher.FluxOnErrorReturn$ReturnSubscriber.onNext(FluxOnErrorReturn.java:162)
      at reactor.core.publisher.MonoDelay$MonoDelayRunnable.propagateDelay(MonoDelay.java:271)
      at reactor.core.publisher.MonoDelay$MonoDelayRunnable.run(MonoDelay.java:286)
      at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:68)
      at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:28)
      at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
      at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
      at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
      at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
      at java.base/java.lang.Thread.run(Thread.java:833)

      2023-10-08T09:41:00.570-07:00 DEBUG 14064 --- [reactor-tcp-nio-3] c.faforever.commons.lobby.FafLobbyApi : Starting session listener
      2023-10-08T09:41:00.572-07:00 INFO 14064 --- [reactor-tcp-nio-3] c.faforever.commons.lobby.FafLobbyApi : Connected to lobby.faforever.com on port 8002
      2023-10-08T09:41:00.741-07:00 ERROR 14064 --- [reactor-tcp-nio-3] c.faforever.commons.lobby.FafLobbyApi : Inbound channel closed with error

      java.net.SocketException: Connection reset
      at java.base/sun.nio.ch.SocketChannelImpl.throwConnectionReset(SocketChannelImpl.java:394)
      at java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:426)
      at io.netty.buffer.UnpooledDirectByteBuf.setBytes(UnpooledDirectByteBuf.java:570)
      at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132)
      at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:357)
      at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:151)
      at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788)
      at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
      at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
      at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
      at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
      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:833)

      2023-10-08T09:41:00.743-07:00 INFO 14064 --- [reactor-tcp-nio-3] c.faforever.commons.lobby.FafLobbyApi : Inbound channel cancelled
      2023-10-08T09:41:00.743-07:00 INFO 14064 --- [reactor-tcp-nio-3] c.faforever.commons.lobby.FafLobbyApi : Outbound channel cancelled
      2023-10-08T09:41:00.744-07:00 INFO 14064 --- [reactor-tcp-nio-3] c.faforever.commons.lobby.FafLobbyApi : Disconnected from server
      2023-10-08T09:41:00.745-07:00 INFO 14064 --- [reactor-tcp-nio-3] c.faforever.commons.lobby.FafLobbyApi : Attempting to reconnect
      2023-10-08T09:41:00.746-07:00 INFO 14064 --- [reactor-tcp-nio-3] c.faforever.commons.lobby.FafLobbyApi : Disconnected from server
      2023-10-08T09:41:00.748-07:00 INFO 14064 --- [reactor-tcp-nio-3] c.faforever.commons.lobby.FafLobbyApi : Attempting to reconnect

      1 Reply Last reply Reply Quote 0
      • maggeM
        magge Global Moderator
        last edited by

        Sorry, apparently, it's related to another hiccup. Was working fine the last hour. We can just be patient for now, until it is sorted out.

        Join a FAFtastic Team

        1 Reply Last reply Reply Quote 1
        • K
          kandaker
          last edited by

          Thanks @magge . This resolved itself for me.

          1 Reply Last reply Reply Quote 0
          • N
            navalynt
            last edited by

            I saw on the Status Page (https://uptime.faforever.com/status/default) there were API problems earlier, but I'm still trying to connect and getting stuck on "Logging In...".

            1 Reply Last reply Reply Quote 0
            • D
              DiatonicScale
              last edited by

              I also can't connect..stuck on logging in

              1 Reply Last reply Reply Quote 1
              • ?
                A Former User
                last edited by

                Discord says it's DDoS

                1 Reply Last reply Reply Quote 1
                • K
                  kandaker
                  last edited by

                  Aha. Thanks for that update @Melanol . That explains why the issue has come back for me. It's not easy for a small service like FAF to protect against DDoS. Perhaps it's some a**hole who got banner from playing.

                  Brutus5000B 1 Reply Last reply Reply Quote 0
                  • Brutus5000B
                    Brutus5000 FAF Server Admin @kandaker
                    last edited by

                    @kandaker said in Can't connect to FAF #2 (as requested):

                    Perhaps it's some a**hole who got banner from playing.

                    That is granted. The attack didn't target "default" endpoints that many services have, but against very specific parts of the FAF infrastructure that are quite unique.

                    Unfortunately FAF was never designed against something like this, so we'll have to do some changes to protect us from future attacks.

                    He said, "I've been to the year 3000
                    Not much has changed, but they live underwater
                    And your great-great-great-granddaughter
                    Is playin' FAF, playin' FAF"

                    1 Reply Last reply Reply Quote 0
                    • Brutus5000B Brutus5000 locked this topic on
                    • First post
                      Last post