Reload plugins is not working in katalon V6.2.0


#21

Hi,

Still same problem with V6.3.0.rc7

Here is the detailled log file :

Error reloading plugins
com.kms.katalon.plugin.models.ReloadPluginsException: Unexpected error occurs during executing reload plugins under account: credential: xxx.xxx@xxx.com, endpoint: https://store.katalon.com/api/products/ks?appVersion=6.3.0
at com.kms.katalon.plugin.service.PluginService.reloadPlugins(PluginService.java:189)
at com.kms.katalon.composer.handlers.ReloadPluginsHandler$1.run(ReloadPluginsHandler.java:61)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.kms.katalon.plugin.models.KStoreClientExceptionWithInfo: Unexpected error occurs during executing get latest plugins
at com.kms.katalon.plugin.service.KStoreRestClient.getLatestPlugins(KStoreRestClient.java:80)
at com.kms.katalon.plugin.service.PluginService.fetchLatestPlugins(PluginService.java:201)
at com.kms.katalon.plugin.service.PluginService.reloadPlugins(PluginService.java:74)
… 2 more
Caused by: org.apache.http.conn.HttpHostConnectException: Connect to store.katalon.com:443 [store.katalon.com/54.86.12.89, store.katalon.com/34.235.178.7] failed: Connection refused: connect
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
at com.kms.katalon.plugin.service.KStoreRestClient.executeGetRequest(KStoreRestClient.java:259)
at com.kms.katalon.plugin.service.KStoreRestClient.getLatestPlugins(KStoreRestClient.java:59)
… 4 more
Caused by: java.net.ConnectException: Connection refused: connect
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)
… 15 more


#22

Hi again,

Solved with manual proxy configuration from my side (proxy configuration from my company).

Hope, it could be same issue for others.

Best regards


#23

Hello @huynguyen,
How I can reload the Katalon Studio version? Sorry, I’m a newbie in using Katalon Studio. I just installed the latest version.

Hello @Arnico,

So after you reload 6.3.0.rc7, you setup the manual proxy config?
Can you show me a sample setup?

Thanks in advance for the assistance.


#24

@geecarl.c.abalajon

Yes, proxy configuration was my problem.
FYI, someone gave me proxy infos (ex : http://xxxx-proxy.yyyyyyyy.com:9999)
Then in Preferences/Katalon/Proxy

  • Proxy Option : Manual proxy configuration
  • Address : xxxx-proxy.yyyyyyyy
  • Port : 9999

#25

Hello @Arnico,

Thanks for the information. Can you assist me on how to reload the Katalon Studio version 6.3.0.rc7?

Thanks again.


#26

You can find v6.3.0.rc7 in this link: https://github.com/katalon-studio/katalon-studio/releases


#27

Hello @Alice and @huynguyen,

I tried using the v6.3.0.rc7 but there is still an error (the same error)
The main issue on our end is not specific to “Reload Plugins” but the “Basic Report” Plugin, as we cannot use it on our end. It is not available in the Project Plugins even though the Basic Plugin is Active on my online account.

With that said, do you have a downloadable version of the Basic Report Plugin, because I’m thinking on manually installing it in Katalon, if possible.

Thanks in advance for your response.


#28

@huynguyen any updates on Geecarl’s issue?


#29

Hi @geecarl.c.abalajon,
Are you behind a proxy? If yes, have you configured the proxy settings in Katalon Studio?


#30

@huynguyen I work together with @geecarl.c.abalajon. Yes, we manually set the proxy settings and afterwards got this different error regarding invalid certification path,


#31


#32

I used the latest version Katalon Studio 6.3.1


#33

Hi @jan.michael.w.cerna,
Please refer to this post and check if it works. Plugin Store behind firewall


#34

I was having the same problem using Ubuntu and Katalon 6.2.2, behind a proxy.
I downloaded Katalon 6.3.1 and problem still occured.
Switched proxy option to manual configuration (under Window -> Katalon Studio Preferences -> Katalon -> Proxy) instead of “Use system proxy configuration” and it started working.


#35

Hi, same problem, Im suspecting its the same problem that Arnico has (company proxy ixsue). Ill check it and Ill get back to you


#36

Thank you, I’m still working with our Tech Team on this. I will keep you posted.


#37

I fixed it. Was a company proxy problem.


#38

While configuring the proxy seems to be the solution, you will sooner or later bump into the issue where the proxy will route your requests to the wrong side of the internet pound. I have to choose now; Either I can reload plugins OR I can run my tests because my application is on the intranet. So much for that design!


#39

When i set the proxy in Katalon to use manual proxy, then i am able to reload plugin, but whenever i change the proxy setting to use System proxy configuration, i am not able to reload plugin. Got error. Can someone help tell me how to fix this?

I assumed the system proxy configuration is the same as browser proxy setting, is it? Where to check the system configuration?


#40

You should use “Manual proxy configuration”.

“Use system configuration” seems to be unreliable.

If you choose “Manual proxy configuration” which lacks “proxy-bypass-list” feature, then your test case scripts will become unable to reach to the host on your interanet such as 172.24.2.3 or 192.168.4.5.

But there is a work around. See: