HPE Morpheus Enterprise
1848585 Members
4292 Online
104033 Solutions
New Discussion

Morpheus Worker behind proxy

 
Not applicable

Morpheus Worker behind proxy

I’m running Morpheus Worker onprem for the Morpheus running in the Cloud to connect to the vCenter in my OnPrem via the Worker.
I installed and reconfigured the worker as mentioned in the documentation, but there are no notes about configuring the worker behind the proxy.
My worker is behind the proxy and I’m getting the following error because the worker in the OnPrem was not able to connect to the Morpheus on the cloud.

2023-10-25_03:45:47.33582 23:45:47.335 [scheduled-executor-thread-2] ERROR c.m.worker.appliance.MorpheusClient - Error Checking Appliance Health: Connect Error: connection timed out: /xx.xx.xx.xx:443
2023-10-25_03:45:47.33585 io.micronaut.http.client.exceptions.HttpClientException: Connect Error: connection timed out: /xx.xx.xx.xx:443
2023-10-25_03:45:47.33586 at io.micronaut.http.client.netty.DefaultHttpClient.lambda$null$35(DefaultHttpClient.java:1245)
2023-10-25_03:45:47.33586 at io.micronaut.http.client.netty.DefaultHttpClient.lambda$addInstrumentedListener$59(DefaultHttpClient.java:3021)
2023-10-25_03:45:47.33586 at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:578)
2023-10-25_03:45:47.33587 at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:552)
2023-10-25_03:45:47.33588 at io.netty.util.concurrent.DefaultPromise.access$200(DefaultPromise.java:35)
2023-10-25_03:45:47.33588 at io.netty.util.concurrent.DefaultPromise$1.run(DefaultPromise.java:502)
2023-10-25_03:45:47.33589 at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
2023-10-25_03:45:47.33589 at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:469)
2023-10-25_03:45:47.33590 at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:503)
2023-10-25_03:45:47.33590 at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)
2023-10-25_03:45:47.33590 at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
2023-10-25_03:45:47.33591 at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
2023-10-25_03:45:47.33591 at java.base/java.lang.Thread.run(Unknown Source)
2023-10-25_03:45:47.33591 Caused by: io.netty.channel.ConnectTimeoutException: connection timed out: /xx.xx.xx.xx:443
2023-10-25_03:45:47.33592 at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:261)
2023-10-25_03:45:47.33592 at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
2023-10-25_03:45:47.33592 at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
2023-10-25_03:45:47.33592 … 7 common frames omitted

I’ve tried setting up the proxy in the following files but nothing worked.
/opt/morpheus-worker/embedded/java/jdk/conf/net.properties and
/opt/morpheus-worker/embedded/cookbooks/morpheus-solo-worker/templates/default/sv-micronaut-run.erb
Any help is appreciated.

Thanks in Advance.

2 REPLIES 2
Not applicable

Re: Morpheus Worker behind proxy

yes the worker VM is configured with HTTP.s requests out.

Ollie-Phillips
HPE Pro

Re: Morpheus Worker behind proxy

Hi Kurt, I’ve no direct experience with the worker and proxies, but is the VM which is host to the worker, configured to use the proxy for HTTP/S requests out?



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo