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; } } }

TS running only locally

dorfi

Hi,

maybe a foolish question..

We have TS running on VMWare with Windows Server 2008 (TS 7.2.1)

All IW Services are properly up and runnning. We have followed the wizard during the installation, using the default configuration in terms of ports
and settings for the different modules.

Locally we digit http://localhost/iw-cc and all is working fine.

Remotely we use http://ip_address/iw-cc and we don't receive any response. If we digit http://ip_address:8080/iw-cc, Jboss properly replies,
but all CGI requests fail

Something odd: locally, if we run telnet on port 80 with localhost, we can estabilish a connection,
but if we run telnet by executing 127.0.0.1 or on port 80, the connection is refused.

It looks like there is some server configuration to setup in terms of allowed URLs. Maybe is there such kind of parameter,
do I miss something in iw.cfg or is it misconfigured?

Find more posts tagged with

Comments

nipper

Or is there an issue with you networking setup on VMWare ? Which networking model are you using ?

You should your IP settings as well.

dorfi

Tried to install Tomcat on the same server and I can telnet remotelly as well..

Adam Stoller

Check the settings in the iw.cfg file to see if they used the hostname, ip address, localhost, or 127.0.0.1.

Ideally you want the first or second of those - if it's the latter two that might cause some of the issue - you can try changing it and restarting the services (or just rebooting) and see if that fixes it.

dorfi

Here comes the configuration

# TeamSite Configuration: you may edit this file, but all formatting changes will be lost.

[iwcgi]

[event_subsystem]
ew_enable=true

[admin_console]
admin_host=localhost
admin_port=8080

[report_center]
reporting_host=localhost
reporting_port=8080

[cssdk_soapservices]
cssdksoapservices_host=localhost
cssdksoapservices_port=8080

[teamsite_servlet_ui]
servlet_host=localhost
servlet_port=8080

[teamsite_templating]

[iwwebd]
default_protocol=http
http_port=80
https_port=443
host=_hostname_

[iwproxy]
customer_webserver_host=_hostname_
iwproxy_host=localhost
iwproxy_port=1080
customer_webserver_port=81

Tried also to replace all localhost with _hostname_ or _ipaddress_

Adam Stoller

Here comes the configuration
...

Tried also to replace all localhost with _hostname_ or _ipaddress_

Is it safe to assume that when you say "_hostname_" or "_ipaddress_" that you were using the actual hostname or ipaddress and just don't want to post that information in the forum?

When you did change it, did you restart all the TeamSite services?

dorfi

Thanks ghoti. It is yes to both questions, and I rebooted the machine too

http://localhost/iw-cc is ok
http://127.0.0.1/iw-cc is ko
http://_hostname_/iw-cc is ko

Trying also to move IIS to port 80 (to check if there are some issues with that port), and it replies with localhost and 127.0.0.1 as well

Struggling with this problem..

dorfi

Maybe something in httpd.conf?

nipper

it is iwwebd.conf.template

Adam Stoller

Trying also to move IIS to port 80

I wouldn't suggest that unless you're also disabling the TeamSite services from starting up.

dorfi

Yes yes, it was just to be sure that a web server would reply properly on that port (tried with another one too). IIS now runs on port 81

All Teamsite Services are started up
The situation is still

http://localhost/iw-cc is ok
http://127.0.0.1/iw-cc is ko
http://_hostname_/iw-cc is ko

iwwebd.conf.template is built based on iw.cfg, isn't it?

dorfi

By setting the hostname instead of localhost wherever inside iw.cfg, it runs with http://_hostname_/iw-cc as well

But absolutely, whenever I try to insert an ipaddress, the connection is refused. I had a look to log files, and access.log seems not to move when I digit http://127.0.0.1/iw-cc

Adam Stoller

By setting the hostname instead of localhost wherever inside iw.cfg, it runs with http://_hostname_/iw-cc as well

But absolutely, whenever I try to insert an ipaddress, the connection is refused. I had a look to log files, and access.log seems not to move when I digit http://127.0.0.1/iw-cc

You shouldn't be using 127.0.0.1 - you should be using the actual IP address of your server. Also - if you have multiple NICs on the server, you need to make sure that TeamSite is listening on the correct NIC / IP address. If I recall correctly, in such a case, you need to play around with the iwwebd.conf.template file and possibly the redirect template file too.

How to update cube in a BDO with enable incremental update.zip

dorfi

Same poor outcome with the real IP address, the only working addresses are localhost and _machinename_
I tried to modify the iwwebd.conf.template, but it seems to have no effect with this case

RonaldV

This is an ip-v4/v6 issue. Add/modify this line:

[PHP]listen 0.0.0.0:80[/PHP]

in your iwwebd.conf.template.

Check http://www.contentdokter.nl/cms-blog/view/teamsite-73-and-ip-v4/ for details.

dorfi

RonaldV, thanks a lot for your suggestion.
I had tried it in my desperation, but on the wrong conf file

This solved the issue

RonaldV

Now that the issue has come up on this forum, what do the experts say:

- is this a problem with Apache?
- or is this a problem with a wrong compilation of the Apache included with TS?

nipper

Now that the issue has come up on this forum, what do the experts say:

- is this a problem with Apache?
- or is this a problem with a wrong compilation of the Apache included with TS?

I have to wonder if there is a reason for this setting. We have been talking about this since 7 was released but 7.3.1 is the same. That was a good spot I had not seen the issue manifest itself in this manner. Typically it just breaks activemq andand search.

Andy

bhat

Locate your 'iwwebd.conf.template' and modify the line

listen 80
to
listen 0.0.0.0:80

After that run 'iwreset -a' as an administrator. requests should work.

Thanks
Bhat