Hi Ruben, That made me being able to login :)
I seem to be getting this: Apr 29 12:25:49 v-144-VM systemd[1]: cloud.service: Main process exited, code=exited, status=1/FAILURE Apr 29 12:25:48 v-144-VM _run.sh[58945]: 12:25:48,272 INFO Agent:314 - Stopping the agent: Reason = sig.kill Apr 29 12:25:48 v-144-VM _run.sh[58945]: at java.base/java.lang.Thread.run(Thread.java:829) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at com.cloud.agent.resource.consoleproxy.ConsoleProxyResource$1.runInContext(ConsoleProxyResource.java:346) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at java.base/java.lang.reflect.Method.invoke(Method.java:566) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at com.cloud.consoleproxy.ConsoleProxy.startWithContext(ConsoleProxy.java:350) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at com.cloud.consoleproxy.ConsoleProxy.start(ConsoleProxy.java:365) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at com.cloud.consoleproxy.ConsoleProxy.startupHttpMain(ConsoleProxy.java:391) Apr 29 12:25:48 v-144-VM _run.sh[58945]: java.lang.NullPointerException Apr 29 12:25:48 v-144-VM _run.sh[58945]: 12:25:48,259 ERROR ConsoleProxy:100 - null Apr 29 12:25:48 v-144-VM _run.sh[58945]: at java.base/java.lang.Thread.run(Thread.java:829) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at com.cloud.agent.resource.consoleproxy.ConsoleProxyResource$1.runInContext(ConsoleProxyResource.java:346) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at java.base/java.lang.reflect.Method.invoke(Method.java:566) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at com.cloud.consoleproxy.ConsoleProxy.startWithContext(ConsoleProxy.java:350) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at com.cloud.consoleproxy.ConsoleProxy.start(ConsoleProxy.java:365) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at com.cloud.consoleproxy.ConsoleProxy.startupHttpMain(ConsoleProxy.java:390) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at com.cloud.consoleproxy.ConsoleProxySecureServerFactoryImpl.createHttpServerInstance(ConsoleProxySecureServerFactoryImpl.java:82) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at com.cloud.consoleproxy.ConsoleProxySecureServerFactoryImpl$1.<init>(ConsoleProxySecureServerFactoryImpl.java:82) Apr 29 12:25:48 v-144-VM _run.sh[58945]: at jdk.httpserver/com.sun.net.httpserver.HttpsConfigurator.<init>(HttpsConfigurator.java:81) Apr 29 12:25:48 v-144-VM _run.sh[58945]: java.lang.NullPointerException: null SSLContext Apr 29 12:25:48 v-144-VM _run.sh[58945]: 12:25:48,249 ERROR ConsoleProxySecureServerFactoryImpl:104 - java.lang.NullPointerException: null SSLContext Apr 29 12:25:48 v-144-VM _run.sh[58945]: 12:25:48,227 INFO ConsoleProxySecureServerFactoryImpl:51 - No certificates passed, recheck global configuration and certificates Apr 29 12:25:48 v-144-VM _run.sh[58945]: 12:25:48,227 INFO ConsoleProxySecureServerFactoryImpl:47 - Start initializing SSL Apr 29 12:25:48 v-144-VM _run.sh[58945]: 12:25:48,226 INFO ConsoleProxySecureServerFactoryImpl:51 - No certificates passed, recheck global configuration and certificates Apr 29 12:25:48 v-144-VM _run.sh[58945]: 12:25:48,225 INFO ConsoleProxySecureServerFactoryImpl:47 - Start initializing SSL Apr 29 12:25:48 v-144-VM _run.sh[58945]: 12:25:48,222 INFO ConsoleProxyResource:104 - Receive ReadyCommand, response with ReadyAnswer Which is a bit strange as in the Events on the panel it says: Successfully completed issuing certificate. domain(s): [v-144-VM, v-144-VM] It didn’t give any issue with uploading them either, I also destroyed the proxy and let it rebuild itself. -- Jimmy From: Ruben Bosch <[email protected]> Date: Monday, 29 April 2024 at 14:15 To: [email protected] <[email protected]> Subject: Re: Replaced SSL now console proxy not working Jimmy, you can run "cloudstack-ssh 169.x.x.x" or "ssh -i /root/.ssh/id_rsa.cloud -p 3922 [email protected]" from the hypervisor running the system VM to SSH into the system VM. On Mon, Apr 29, 2024 at 2:09 PM Jimmy Huybrechts <[email protected]> wrote: > Hi, > > So I replaced the SSL certficate today since it uses lets encrypt. > > My secondary storage worked fine after recreation, but it seems my > consoleproxy doesn’t as it shows agent state disconnected, connecting, > disconnected. > > Now obviously I don’t have any console now so I can’t see what is wrong > with it. :) how to connect to it over for example SSH (as I get connection > refused) or a different way? So I can see what is wrong with it and debug. > I would guess it has something to do with SSL but without debugging it’s > anyone’s guess. > > -- > Jimmy >
