nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Teamsite content center IWPROXY issue

abhijitdd

Hello we are using teamsite content center version - Interwoven TeamSite 6.7.2 Service Pack 2.

We are facing this issue -
when user tries to download any file by clicking on filename displayed in browser UI we get below error -
Connection Failed
iwproxy was unable to open a connection to:
{our server's name}:81
Reason: Transport endpoint is not connected.

Can you please help me with this? I am quite new to Teamsite.

Find more posts tagged with

Comments

Bhargav Coca

whats your Teamsite default port? it should be 80, if you have set it while installation to 81 then it is 81. So your UI is working fine, but when you download you are getting this error?

A screenshot of the error would be really help ful. And also paste what you see on the address bar?

for this http://yourservername:80/
and
http://yourservername:81/

Thanks

Adam Stoller

Hello we are using teamsite content center version - Interwoven TeamSite 6.7.2 Service Pack 2.

We are facing this issue -
when user tries to download any file by clicking on filename displayed in browser UI we get below error -
Connection Failed
iwproxy was unable to open a connection to:
{our server's name}:81
Reason: Transport endpoint is not connected.

Can you please help me with this? I am quite new to Teamsite.

Clicking on a filename does not "download" a file - it attempts to "preview" the file. This means that TeamSite sends the data to whatever "customer web server" you configured.

This then leads to the question - did you configure a "customer web server"?

On Windows, this is usually IIS, though sometimes Apache or something else.
On Unix this is usually Apache, though sometimes something else.

Normally, the customer web server is configured to run on port 81 (iwwebd, TeamSite's internal Apache server is normally run on port 80 to render the UI)

If you don't know what any of this means you should:

abhijitdd

Hello Lilley,

I have already pasted the error text in my post. Its the only thing that gets displayed in my browser. Also I tried these -

http://my server name:80/ - here Teamsite UI gets displayed.

http://my server name:81/ here I get message Internet Explorer cannot display webpage.

Regards

Adam Stoller

Hello Lilley,

I have already pasted the error text in my post. Its the only thing that gets displayed in my browser. Also I tried these -

http://my server name:80/ - here Teamsite UI gets displayed.

http://my server name:81/ here I get message Internet Explorer cannot display webpage.

Regards

Exactly - you do not have a "Customer Web Server" configured - see my previous post.

abhijitdd

actually this was working fine till some days back. That is why I am confused why it has suddenly stopped working.

Also I checked my iw.cfg file -

It has below contents for iwproxy -
[iwproxy]
iwproxy_port=1080

## The port that the customer's web server can be found at. Make sure that this
## does not overlap with iwwebd, iwproxy, or the servlet engine.
customer_webserver_port=81

And this was not changed at all. Then what could be the problem?

Regards.

Adam Stoller

...
And this was not changed at all. Then what could be the problem?

Regards.

Uhm, let's see - maybe the customer web server was shut down, crashed, or otherwise stopped working?

abhijitdd

per my knowledge the name of the server on which teamsite is installed and that of the customer web server to which this iwproxy is trying to connect are same. And Teeamsite application is working fine which means server on which it is installed is working fine. So what could be the problem here?

Adam Stoller

per my knowledge the name of the server on which teamsite is installed and that of the customer web server to which this iwproxy is trying to connect are same. And Teeamsite application is working fine which means server on which it is installed is working fine. So what could be the problem here?

Clearly you have not read the manuals nor had that much experience with TeamSite - so I'll try to explain this once again: