Hi All, we have just deployed v 0.50.11 to our UAT servers and when we open the Source & Destination within the Settings tab the system errors. I think it's due to our company proxy server.

2023-07-27 23:27:53 ERROR i.a.s.a.ApiHelper(execute):40 - Unexpected Exception
io.airbyte.commons.server.errors.InternalServerKnownException: Unable to process retrieved latest destination definitions list
	at io.airbyte.commons.server.handlers.DestinationDefinitionsHandler.buildDestinationDefinitionRead(DestinationDefinitionsHandler.java:132) ~[io.airbyte-airbyte-commons-server-0.50.11.jar:?]
	at io.airbyte.commons.server.handlers.DestinationDefinitionsHandler.lambda$toDestinationDefinitionReadList$0(DestinationDefinitionsHandler.java:145) ~[io.airbyte-airbyte-commons-server-0.50.11.jar:?]
	at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197) ~[?:?]
	at java.util.AbstractList$RandomAccessSpliterator.forEachRemaining(AbstractList.java:722) ~[?:?]
	at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509) ~[?:?]
	at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499) ~[?:?]
	at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:921) ~[?:?]
	at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:?]
	at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:682) ~[?:?]
	at io.airbyte.commons.server.handlers.DestinationDefinitionsHandler.toDestinationDefinitionReadList(DestinationDefinitionsHandler.java:146) ~[io.airbyte-airbyte-commons-server-0.50.11.jar:?]
	at io.airbyte.commons.server.handlers.DestinationDefinitionsHandler.listDestinationDefinitionsForWorkspace(DestinationDefinitionsHandler.java:185) ~[io.airbyte-airbyte-commons-server-0.50.11.jar:?]
	at io.airbyte.server.apis.DestinationDefinitionApiController.lambda$listDestinationDefinitionsForWorkspace$6(DestinationDefinitionApiController.java:125) ~[io.airbyte-airbyte-server-0.50.11.jar:?]
	at io.airbyte.server.apis.ApiHelper.execute(ApiHelper.java:26) ~[io.airbyte-airbyte-server-0.50.11.jar:?]
	at io.airbyte.server.apis.DestinationDefinitionApiController.listDestinationDefinitionsForWorkspace(DestinationDefinitionApiController.java:125) ~[io.airbyte-airbyte-server-0.50.11.jar:?]
	at io.airbyte.server.apis.$DestinationDefinitionApiController$Definition$Exec.dispatch(Unknown Source) ~[io.airbyte-airbyte-server-0.50.11.jar:?]
	at io.micronaut.context.AbstractExecutableMethodsDefinition$DispatchedExecutableMethod.invoke(AbstractExecutableMethodsDefinition.java:371) ~[micronaut-inject-3.9.4.jar:3.9.4]
	at io.micronaut.context.DefaultBeanContext$4.invoke(DefaultBeanContext.java:594) ~[micronaut-inject-3.9.4.jar:3.9.4]
	at io.micronaut.web.router.AbstractRouteMatch.execute(AbstractRouteMatch.java:303) ~[micronaut-router-3.9.4.jar:3.9.4]
	at io.micronaut.web.router.RouteMatch.execute(RouteMatch.java:111) ~[micronaut-router-3.9.4.jar:3.9.4]
	at io.micronaut.http.context.ServerRequestContext.with(ServerRequestContext.java:103) ~[micronaut-http-3.9.4.jar:3.9.4]
	at io.micronaut.http.server.RouteExecutor.lambda$executeRoute$14(RouteExecutor.java:659) ~[micronaut-http-server-3.9.4.jar:3.9.4]
	at reactor.core.publisher.FluxDeferContextual.subscribe(FluxDeferContextual.java:49) ~[reactor-core-3.5.5.jar:3.5.5]
	at reactor.core.publisher.InternalFluxOperator.subscribe(InternalFluxOperator.java:62) ~[reactor-core-3.5.5.jar:3.5.5]
	at reactor.core.publisher.FluxSubscribeOn$SubscribeOnSubscriber.run(FluxSubscribeOn.java:194) ~[reactor-core-3.5.5.jar:3.5.5]
	at io.micronaut.reactive.reactor.instrument.ReactorInstrumentation.lambda$init$0(ReactorInstrumentation.java:62) ~[micronaut-runtime-3.9.4.jar:3.9.4]
	at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:84) ~[reactor-core-3.5.5.jar:3.5.5]
	at reactor.core.scheduler.WorkerTask.call(WorkerTask.java:37) ~[reactor-core-3.5.5.jar:3.5.5]
	at io.micronaut.scheduling.instrument.InvocationInstrumenterWrappedCallable.call(InvocationInstrumenterWrappedCallable.java:53) ~[micronaut-context-3.9.4.jar:3.9.4]
	at java.util.concurrent.FutureTask.run(FutureTask.java:317) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
	at java.lang.Thread.run(Thread.java:1589) ~[?:?]
Caused by: java.lang.NullPointerException: Cannot invoke "String.length()" because "this.input" is null
	at java.net.URI$Parser.parse(URI.java:3161) ~[?:?]
	at java.net.URI.<init>(URI.java:620) ~[?:?]
	at io.airbyte.commons.server.handlers.DestinationDefinitionsHandler.buildDestinationDefinitionRead(DestinationDefinitionsHandler.java:122) ~[io.airbyte-airbyte-commons-server-0.50.11.jar:?]

I've added HTTP_PROXY= & HTTPS_proxy= to the .env file and also added then under the worker in the yaml file

Based on the error logs you've provided, it seems like there's an issue with the destination definitions list. The error message indicates a

NullPointerException

which means that some expected value is null. However, without more context or information, it's hard to pinpoint the exact cause of the issue. It could be related to your company's proxy server as you've mentioned, or it could be a bug in the version of Airbyte you're using. Here are a few steps you can take to troubleshoot this issue: 1. Check your destination configurations: Ensure that all the necessary configurations for your destination are correctly set up. 2. Update Airbyte: You're currently using version 0.50.11. It might be helpful to update to the latest version of Airbyte, as the issue you're experiencing could have been resolved in a more recent release. 3. Check your network settings: If you suspect that your company's proxy server is causing the issue, you might want to check your network settings and make sure that Airbyte is able to communicate with the outside network. 4. Reach out to Airbyte support: If you're still experiencing the issue after trying the above steps, it might be helpful to reach out to Airbyte's support team. You can do this through their [Slack channel](https://airbytehq.slack.com/archives/C021JANJ6TY) or [forum](https://discuss.airbyte.io). Remember to provide as much information as possible when reaching out for support, including any error logs and the steps you've taken to troubleshoot the issue. This will help the support team diagnose and resolve your issue more effectively.