| Author |
Message |
![[Post New]](/Sysforums/templates/default/images/icon_minipost_new.gif) 13/06/2008 04:58:00
|
Haim
SysAider
Joined: 15/04/2008
Messages: 2449
Offline
|
SysAid, by default will use port 8080
If you would like to change it, please follow the below instructions:
To change the port SysAid is listening to, please edit the ...\SysAidServer\tomcat\conf\server.xml file and look for the port="XXXX" (replace XXXX with the current port number). Change this value to the requested port number.
After saving changes, please restart the “Sys Aid Server” service, and try to access SysAid on the new port.
NOTE: If you will come across port 8005 – do not change it, it is not your server's port. It's Tomcat internal shutdown port, and shouldn't be changed unless you have another program running on that same port.
|
Pushing IT forward |
|
|
27/01/2009 06:43:11
|
Alex.Moreira
SysAider
Joined: 15/01/2009
Messages: 47
Location: Brazil
Offline
|
Haim, is there any way for me NOT TO use port on the address? Like...
http://myserver.com/sysaid instead of http://myserver.com:8080/sysaid ?
I changed my server.xml at Tomcat/conf, but couldn't manage to make it work without a port, even trying the port:"80" there.
Any suggestion? =]
Thanks,
Alexandre Taitson
|
|
|
27/01/2009 06:50:33
|
Haim
SysAider
Joined: 15/04/2008
Messages: 2449
Offline
|
Hey Alex.Moreira,
If you will change the port to port 80, then you wouldn't need to type the port number (since all web browsers are going for this port automatically).
What happens after you change the port to 80?
|
Pushing IT forward |
|
|
27/01/2009 07:12:38
|
Alex.Moreira
SysAider
Joined: 15/01/2009
Messages: 47
Location: Brazil
Offline
|
Haim wrote:Hey Alex.Moreira,
If you will change the port to port 80, then you wouldn't need to type the port number (since all web browsers are going for this port automatically).
What happens after you change the port to 80?
I restart Tomcat, and when I try to open SysAid, it fails to load page.
Just as trying to access a page that doesn't exist.
edit: And I know it 'works', because if I set it to other ports, it works.
I set it to port 9000, worked... Set to port 8000, worked, set to many others and worked, but I couldn't set it to port 80 in order to remove the port from the address.
This message was edited 1 time. Last update was at 27/01/2009 07:19:23
|
|
|
27/01/2009 08:19:17
|
Haim
SysAider
Joined: 15/04/2008
Messages: 2449
Offline
|
Alex.Moreira .
This issue usually happens when you have a different software running on port 80 on the same machine, so a port conflict occur and then tomcat shut down.
Please stop the software that's listening to port 80 and then you will be able to allow SysAid to run on port 80.
Best regards.
Haim
|
Pushing IT forward |
|
|
27/01/2009 09:12:43
|
Alex.Moreira
SysAider
Joined: 15/01/2009
Messages: 47
Location: Brazil
Offline
|
Haim wrote:Alex.Moreira .
This issue usually happens when you have a different software running on port 80 on the same machine, so a port conflict occur and then tomcat shut down.
Please stop the software that's listening to port 80 and then you will be able to allow SysAid to run on port 80.
Best regards.
Haim
What I found out is that all ports below 1024 are privileged ports that can't be used by other stuff that doesn't have Root access.
Trying to work this around now, I made it successfully through Iptables, redirecting the access from port 80 to 8080, therefore I could access SysAid without typing the port in the IP address. It worked perfectly and could surely be done if you are leaving that computer as internal server only, with no access to internet, as when you do this, all access to port:80 is redirected to port:8080... So when you try to access google, it actually tries www.google.com:8080, that doesn't exist.
So.. back to sketch table. This will work, and it will work today.
|
|
|
27/01/2009 11:20:14
|
Alex.Moreira
SysAider
Joined: 15/01/2009
Messages: 47
Location: Brazil
Offline
|
For Linux users, this is what I ended up doing (and worked perfectly, indeed)
If you don't want to need the 'port' on the address field in order to access SysAid, and want your clients to access it the same way, you just do this:
On your System prompt, run this line:
"sudo" is for the command to run in 'root mode', without being root. (still need the password)
Iptables is a 'port forwarding' function.
PREROUTING parameter makes OTHER computers that try to access yours to be automatically 'under the rule' you created. (in this case, be redirected from port 80 to port 8080).
This second line's difference is on the "PREROUTING", here it was substituted by "OUTPUT", that makes YOUR computer be redirected from port 80 to port 8080 (on this line of command, but you can change it for any other ports according to your needs).
That way, your computer won't need to specify the port either, BUT I wouldn't advise it to be used if you will use the computer you put SysAid in, for other stuff.
By doing this second line of command, you are telling your computer to redirect all accesses you make on port 80, to port 8080... That includes navigating in the internet, so you'll always try to access "www.google.com:8080" which doesn't exist (its www.google.com:80), so you won't be able to access any website.
edit: If instead of the second line of command (OUTPUT line), you use this:
sudo iptables -t nat -I OUTPUT -p tcp -d INSERT_YOUR_IP_HERE --dport 80 -j REDIRECT --to-ports 8080
It will redirect only the accesses into YOUR computer, to port 8080, leaving you free to use the internet as you wish.
After doing the lines of command, run this to test it out:
You should see something like this:
If you see this, it worked and you can try accessing SysAid with no port on address (remember to change the ports I used for the ports you want to use).
But if you just leave it like this, it will be changed back whenever you restart your computer, therefore you must do 2 more things before rebooting:
First, save these iptables configurations:
sudo iptables-save > /etc/iptables.conf
That will save your iptables so you can 'use it later' (automatically).
And then, you edit the file /etc/network/interfaces, and add this line in the end of the commands there:
pre-up iptables-restore < /etc/iptables.conf
Now it will run itself every time you reboot, re-setting these configurations so no one will ever need to specify the port when trying to use SysAid (and you'll need if you want to, but if you have this computer as Server only, and its there, unused by anyone else, then have the second line just so you don't need too).
In short:
1. Run first line of command:
2. Run second line of command (optional, read above):
3. Test the Iptables:
4. Save the changes:
sudo iptables-save > /etc/iptables.conf
5. Edit /etc/network/interface file, adding this line:
pre-up iptables-restore < /etc/iptables.conf
And its done.
What I did here was to run only the first line of command, so the End-users won't need the port to be specified. I still have to do so, but as in the Admin side here, I don't care at all about this, but for the End-users that need to access the Help Desk, try to teach them all what a port is and how to do it... Not a very good idea...
In the end, it's all working as I want to.
I hope it helps more people with this same issue or needing to do the same thing as I did.
Good luck and thanks for the help,
Alexandre Taitson Moreira
This message was edited 3 times. Last update was at 27/01/2009 11:52:40
|
|
|
05/05/2009 12:15:08
|
scumgrief
Super SysAider
Joined: 25/02/2009
Messages: 60
Offline
|
Anyone have a tip on removing the port from the address in a Windows environment?
|
|
|
07/05/2009 07:58:35
|
techguy
SysAid Mod
Joined: 11/06/2008
Messages: 1451
Location: England
Offline
|
if you follow the advice in the first post and change it to port 80 the port number will no longer be required.
|
Need help? Try the SysAid wiki first! - http://sites.google.com/site/sysaidwiki |
|
|
11/05/2011 12:38:18
|
PeterA
Super SysAider
Joined: 28/06/2010
Messages: 80
Offline
|
I have my main sysaid server working properly on port 80 but I just set up a Sysaid 8 beta server and attempted the same thing with it. It works fine on 8080 but if I make the change to 80 I get a blank page. No errors just no response.
|
|
|
06/07/2011 15:27:48
|
PDuhaime
SysAider
Joined: 29/06/2011
Messages: 1
Offline
|
For those running windows server 2008 and what to change SysAid website to port 80 must do the following things:
1) Make sure IIS is not installed.
2) Stop and disable both the "World Wide Web Publishing Service" and "Windows Remote Management (WS-Management)" in server manager.
3) Configure C:\Program Files (x86)\SysAidServer\tomcat\conf\server.xml to port 80
This message was edited 1 time. Last update was at 06/07/2011 15:47:26
|
|
|
![[Up]](/Sysforums/templates/default/images/icon_up.gif){kind=icon}
