GRPC server certificate and key are mounted but still not recognized #6225
-
|
Hi, I have deployed Nextcloud AIO and configured the nextcloud-aio-talk container manually using Portainer. Still, I get this warning in the logs: Thank you in advance for your help! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
Hi, as far as I know, grpc is only needed if you run the talk high-performance-backend in cluster mode, which we are not doing. So you can ignore the warning. Are you running into a specific problem or why are you trying to configure a grpc certificate? |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the clarification! I was trying to ensure encrypted internal communication, thinking it was necessary for production hardening. Thanks again for the help! |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the clarification. Yes, I now understand that the gRPC certificate is only required when using the high-performance backend in cluster mode, with multiple backend nodes communicating securely via gRPC. Since I’m currently running a single backend instance through Nextcloud AIO, it makes sense that gRPC encryption is not necessary and the warnings can safely be ignored. I appreciate your guidance! Thanks again for your time and support! Best regards, |
Beta Was this translation helpful? Give feedback.
Hi, as far as I know, grpc is only needed if you run the talk high-performance-backend in cluster mode, which we are not doing. So you can ignore the warning.
Are you running into a specific problem or why are you trying to configure a grpc certificate?