RAK7268C Gateway, dropping downlink message from the AWS after firmware upgrade

Issue:
Downlink message is been dropped by the gateway which is preventing it from receiving joinAccept or any downlink message.

Setup:
firmware version : 1.3.5_RAK b135
Server:
Aws Iot core lorawan
Details:
I just got this new Rak7268 gateways which came with firmware version 1.3.5 onboard and am using the BaseStation mode to connect to aws iot core lorawan network, connecting the gateway to the server is working fine, but when an end node try to join network the gateway never receive the joinaccept downlink from the server, i checked and confirm that aws is sending the JoinAccept message. it seems like the message is been dropped by the gateway, below is the systemLog from the gateway, any ideas on how i can resolve this issue?

ri Nov 18 14:02:34 2022 kern.info kernel: [ 7439.900000] syslog.sh (2486): drop_caches: 1
Fri Nov 18 14:02:39 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:02:42 2022 user.notice data-broker: data-broker timeout, restart it
Fri Nov 18 14:02:45 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:02:52 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:02:58 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:03:05 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:03:12 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:03:17 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:03:25 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:03:30 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:03:37 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:03:43 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:03:50 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:03:57 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:04:03 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:04:09 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:04:16 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:04:22 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:04:28 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:04:35 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:04:42 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:04:48 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:04:54 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:05:01 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:05:07 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:05:14 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:05:20 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:05:27 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:05:33 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:05:39 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:05:46 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:05:47 2022 user.notice data-broker: data-broker timeout, restart it
Fri Nov 18 14:05:52 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:05:59 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:06:05 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:06:12 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
Fri Nov 18 14:06:18 2022 user.warn basicstation[21518]: [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped

same here i’m getting the following error now:
WS upgrade failed with HTTP status code: 400
and the gateway is no longer connected to TTN.
log details:

Tue Nov 22 10:11:05 2022 user.info basicstation[10721]: [AIO:INFO] tc has no cert configured - running server auth and client auth with token
Tue Nov 22 10:11:05 2022 user.debug basicstation[10721]: [TCE:VERB] Connecting to MUXS...
Tue Nov 22 10:11:05 2022 user.err basicstation[10721]: [AIO:ERRO] [5] WS upgrade failed with HTTP status code: 400
Tue Nov 22 10:11:05 2022 user.debug basicstation[10721]: [TCE:VERB] Connection to MUXS closed in state 3
Tue Nov 22 10:11:05 2022 user.debug basicstation[10721]: [SYS:VERB] Sys state 2
Tue Nov 22 10:11:05 2022 user.info basicstation[10721]: [TCE:INFO] INFOS reconnect backoff 10s (retry 1)

Hello all,
i solved my connection issue after the upgrade as follows:
after upgrading for some reason the token under LoRa Network>>Network Settings: Basic Station/token had an extra Bearer Authorization injected right before the authorization token see the image below… as soon as i removed that Bearer Authorization: it connected correctly and worked as expected… not sure where that came from and how it was injected in there, happen after upgrading to firmware 1.3.5.
image

hope this helps others with reconnection issues.
Cheers,
Jay