You are viewing limited content. For full access, please sign in.

Question

Question

Web tools agent connection refused

asked on November 24

Intermittently we just get a Please Wait flashing message when trying to view a document in Web Client. In the Chrome console it says plugin.laserfichelocalhost.com connection refused over and over flooding the console continuously.

We checked under Options Advanced and it shows the web tools agent is online and connected without any errors.

We can ping plugin.laserfichelocalhost.com and resolve to the 127 address.

We checked the Web Tools Agent log in AppData and there are no errors.

How do we see why the connection refused? We need an interface for this agent because anytime we get a problem we can never see what is wrong.

0 0

Answer

APPROVED ANSWER SELECTED ANSWER
replied on November 24

What kind of document are you trying to view? WebTools Agent is not used when opening documents in the document viewer. 

If the Options page shows WebTools Agent connected, then the error connecting to plugin.laserfichelocahost.com are not relevant (it's normal to see 3 mentions of it as WebTools Agent chooses an available port. If it connects, you'll see 2 errors on the ports it does not use). But again, not used when opening the document viewer. 

1 0
replied on November 24

Oh this explains it! We saw 2 when the page was loading normally, but we had a situation that caused the page to refresh over and over again and that was why it was endlessly spamming. I have a support ticket open for the refreshing issue.

0 0

Replies

replied on November 24

If this is Chrome Specific and the version of Chrome is 142, The user may have selected "deny" when prompted by webtools agent to connect. Navigate to "chrome://settings/content/" select the Laserfiche URL and scroll to the bottom. Change "Local network access" to "allow" or "ask" if you want to be prompted again. 

0 0
replied on November 24

The toggle to enable it is greyed out.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.