I installed Qlik Web Connectors on my central node in a multi node environment. I followed the basic instruction and I'm able to set up web connector and run it locally when I'm in my app, using localhost as my server connection. This is obviously because when I'm running script from the hub, it runs on the central node. However, when I have the scheduler run this, on a rim node, it fails. I have 2 issues.
First, I get errors when I try to create a new web file data connection. If I use the server name for my connection to the web connectors, I get various errors. For example, my server name is hypothetically "QLKTST01". When I create the web connection, it fails when I try to add it with the following error message:
The only way to make it work is if I create it as "http://localhost:5555/web/". I get an access is denied error but I can click through it and get results.
Second, what kind of changes do I need to make changes in my deploy.config file? Do I need to enable "AllowRemoteAccess"? It's not clear in the documentation if this is for remote access of the rim nodes under the service account. What I'm reading is that this is for users to access the web connector interface to generate their own script.
These two issues sound like the same underlying issue to me.
In your first para you say you can create and use a connection successfully using localhost but in the next para you say you are getting 'access denied' - where is this happening from compared to the first para?
From what you say if you need to support reloads from nodes other than where QWC is running then you will need to set AllowRemoteAccess to true and I would also say set up forms auth users for the web interface and require SSL as described here:
With AllowRemoteAccess = true by default QWC should listen on the machine name so I would expect version 1. in your list below to work. But I would recommend ensuring you can ping this from the machine(s) where you need to connect from and if this doesn't work you could use the HostnameOverride setting in deploy.config to set e.g. your 3. value above.