-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Response message is failed: Plugin not authorized #537
Comments
Hi @mapleting88, I think that you bumped into this problem because of the wrong configuration of devicehive-ws-proxy service. You should disable Plugin Manager. |
[cid:_Foxmail.1@da03ae6f-bd5f-a1ba-d8df-03a0c57fa85d]
this is the pic of the config.json in the directory devicehive-ws-proxy-master/src
…________________________________
[email protected]
From: Ihor<mailto:[email protected]>
Date: 2019-03-21 16:54
To: devicehive/devicehive-java-server<mailto:[email protected]>
CC: mapleting88<mailto:[email protected]>; Mention<mailto:[email protected]>
Subject: Re: [devicehive/devicehive-java-server] Response message is failed: Plugin not authorized (#537)
Hi @mapleting88<https://github.com/mapleting88>,
I think that you bumped into this problem because of the wrong configuration of devicehive-ws-proxy service. You should disable Plugin Manager.
Could you please share with me your devicehive-ws-proxy configuration?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#537 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Ah0A0uOURahedqH1ubw0bEqBJUghGhloks5vY0iqgaJpZM4cA6N6>.
|
i just start up one process using the port 3000,Should i start up an other process with port 3001?
…________________________________
[email protected]
From: Ihor<mailto:[email protected]>
Date: 2019-03-21 16:54
To: devicehive/devicehive-java-server<mailto:[email protected]>
CC: mapleting88<mailto:[email protected]>; Mention<mailto:[email protected]>
Subject: Re: [devicehive/devicehive-java-server] Response message is failed: Plugin not authorized (#537)
Hi @mapleting88<https://github.com/mapleting88>,
I think that you bumped into this problem because of the wrong configuration of devicehive-ws-proxy service. You should disable Plugin Manager.
Could you please share with me your devicehive-ws-proxy configuration?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#537 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Ah0A0uOURahedqH1ubw0bEqBJUghGhloks5vY0iqgaJpZM4cA6N6>.
|
Thx for your help,I have resolved the problem.We must start up to process to listen the inner messages and the outer messages.But I only started up one,So the outer system can not receive the response messages.
Thank you for an other once.
…________________________________
[email protected]
From: Ihor<mailto:[email protected]>
Date: 2019-03-21 16:54
To: devicehive/devicehive-java-server<mailto:[email protected]>
CC: mapleting88<mailto:[email protected]>; Mention<mailto:[email protected]>
Subject: Re: [devicehive/devicehive-java-server] Response message is failed: Plugin not authorized (#537)
Hi @mapleting88<https://github.com/mapleting88>,
I think that you bumped into this problem because of the wrong configuration of devicehive-ws-proxy service. You should disable Plugin Manager.
Could you please share with me your devicehive-ws-proxy configuration?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#537 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Ah0A0uOURahedqH1ubw0bEqBJUghGhloks5vY0iqgaJpZM4cA6N6>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I setup my DeviceHive-3.5.0 via manual installation,when I start up the devicehive-backend with the devicehive-backend-3.5.0-boot.jar, it reports a error "Response message is failed: Plugin not authorized"
the whole message is:
2019-03-21 15:53:23.875 [XNIO-1 task-13] WARN c.d.p.c.WebSocketKafkaProxyClient - Response message is failed: Plugin not authorized
2019-03-21 15:53:23.876 [XNIO-1 task-13] ERROR io.undertow.websockets.core.request - UT025007: Unhandled exception for annotated endpoint com.devicehive.proxy.client.WebSocketKafkaProxyClient@70d4e44e
com.devicehive.exceptions.HiveException: Response message is failed: Plugin not authorized
at com.devicehive.proxy.client.WebSocketKafkaProxyClient.lambda$onMessage$0(WebSocketKafkaProxyClient.java:114) ~[devicehive-proxy-ws-kafka-impl-3.5.0.jar!/:3.5.0]
at java.util.Collections$SingletonList.forEach(Collections.java:4822) ~[na:1.8.0_201]
at com.devicehive.proxy.client.WebSocketKafkaProxyClient.onMessage(WebSocketKafkaProxyClient.java:109) ~[devicehive-proxy-ws-kafka-impl-3.5.0.jar!/:3.5.0]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_201]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_201]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_201]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_201]
at io.undertow.websockets.jsr.annotated.BoundMethod.invoke(BoundMethod.java:87) ~[undertow-websockets-jsr-1.4.20.Final.jar!/:1.4.20.Final]
at io.undertow.websockets.jsr.annotated.AnnotatedEndpoint$2.onMessage(AnnotatedEndpoint.java:142) ~[undertow-websockets-jsr-1.4.20.Final.jar!/:1.4.20.Final]
at io.undertow.websockets.jsr.FrameHandler$7.run(FrameHandler.java:281) ~[undertow-websockets-jsr-1.4.20.Final.jar!/:1.4.20.Final]
at io.undertow.websockets.jsr.ServerWebSocketContainer$1.call(ServerWebSocketContainer.java:162) ~[undertow-websockets-jsr-1.4.20.Final.jar!/:1.4.20.Final]
at io.undertow.websockets.jsr.ServerWebSocketContainer$1.call(ServerWebSocketContainer.java:159) ~[undertow-websockets-jsr-1.4.20.Final.jar!/:1.4.20.Final]
at io.undertow.websockets.jsr.ServerWebSocketContainer.invokeEndpointMethod(ServerWebSocketContainer.java:575)
What can I do to resove it? Is there any service must be started befor?
The text was updated successfully, but these errors were encountered: