Stuck on Connected to WebSocket
Tavinen opened this issue · 5 comments
I tried to run the bot but it was not working when I tried to run a command and the funniest thing was that if i put token as blank and run the bot, it ran well except for that command saying it can't connect to any account
This is the log
Picked up _JAVA_OPTIONS: -Xmx6144M
| _ _ / / __ \ _ | ___ \ _ \ / || _ | | | | \ | | _ \ ___ | _ |/ _ \ | ___ \ _
| | | | | | \ --.| / \/ | | | |_/ / | | | \ --. | | | | | | | | | | | | |/ /| | | / /\ | |/ / | | |
| | | | | | --. \ | | | | | /| | | | --. | | | | | | | . ` | | | | ___ | | | | _ || /| | | |
| |/ / | |/_/ / _/\ _/ / |\ | |/ / /_/ /\ _/ / || | |\ | |/ /| |/ /\ _/ / | | || |\ | |/ /
|/ _/_/ _/_/_| _|/ _/ _/ _/_| _// _/ _/_| |/_| _|__/
Discord Soundboard (v3.0.4)
2020-10-28 22:54:28.065 INFO 12524 --- [ main] n.d.discordsoundboard.MainController : Starting MainController v3.0.4 on user-PC with PID 12524 (C:\Users\user\Desktop\내꺼\Discord Bots\DiscordSoundboard\lib\DiscordSoundboard-3.0.4.jar started by user in C:\Users\user\Desktop\내꺼\Discord Bots\DiscordSoundboard\bin)
2020-10-28 22:54:28.070 INFO 12524 --- [ main] n.d.discordsoundboard.MainController : No active profile set, falling back to default profiles: default
2020-10-28 22:54:29.449 INFO 12524 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data repositories in DEFAULT mode.
2020-10-28 22:54:29.540 INFO 12524 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 78ms. Found 2 repository interfaces.
2020-10-28 22:54:30.075 INFO 12524 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-10-28 22:54:31.092 INFO 12524 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http)
2020-10-28 22:54:31.111 INFO 12524 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]
2020-10-28 22:54:31.111 INFO 12524 --- [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.27]
2020-10-28 22:54:31.234 INFO 12524 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
2020-10-28 22:54:31.234 INFO 12524 --- [ main] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 3083 ms
2020-10-28 22:54:31.503 INFO 12524 --- [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [name: default]
2020-10-28 22:54:31.720 INFO 12524 --- [ main] org.hibernate.Version : HHH000412: Hibernate Core {5.4.6.Final}
2020-10-28 22:54:31.988 INFO 12524 --- [ main] o.hibernate.annotations.common.Version : HCANN000001: Hibernate Commons Annotations {5.1.0.Final}
2020-10-28 22:54:32.140 INFO 12524 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting...
2020-10-28 22:54:32.423 INFO 12524 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Start completed.
2020-10-28 22:54:32.469 INFO 12524 --- [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
2020-10-28 22:54:33.531 INFO 12524 --- [ main] o.h.e.t.j.p.i.JtaPlatformInitiator : HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]
2020-10-28 22:54:33.543 INFO 12524 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default'
2020-10-28 22:54:35.833 INFO 12524 --- [ main] net.dv8tion.jda.api.JDA : Login Successful!
2020-10-28 22:54:36.258 INFO 12524 --- [nWS-WriteThread] n.d.j.internal.requests.WebSocketClient : Connected to WebSocket
I have the same issue! I've tried updating Java, my drivers, and restarting after each. Still gets stuck after "Connected to Websocket"
I have the same issue. The bot won't work anymore and is stuck on Websocket
Same issue here. Have changed nothing with settings for weeks.
I think the remote server for the bot has been taken down. I have the same issue.