5.0-Nano: Known Issues: Difference between revisions

From The Uniform Server Wiki
Jump to navigation Jump to search
(New page: {{Nav 5.0-Nano}} '''Known issues and problems''' This page contains known issues and problems, where applicable offers solutions. == Vista == * Problem: Earlier versions of Vista have p...)
 
mNo edit summary
Line 3: Line 3:


This page contains known issues and problems, where applicable offers solutions.  
This page contains known issues and problems, where applicable offers solutions.  
== Servers not starting ==
'''Q)''' Apache and or MySQL servers will not start why?
'''A)''' If port 80 is being used by another service or server Uniform Server will not start. Before starting UniServer make sure you do not have another service running on Port 80.
Run '''''Server Status''''' from UniTray: Check ports are free to use.
If they are in use try the following solutions:
'''''[[#top | Top]]'''''
=== port 80 kill process XP Pro ===
You can kill the processes that use port 80 on XP Pro as follows:
# Start the Command Prompt and then type '''netstat -ano | find "LISTENING" | find ":80"'''
## You'll see a bunch of stuff like "TCP x.x.x.x:80 x.x.x.x:0 LISTENING '''number'''", what we're interested in here is '''number''', if there are more than one (which normally shouldn't happen), repeat the steps below for each one
# Type '''tasklist /SVC /FI "PID number"''', replace number with the one you saw after executing the first command.
## You'll see 3 lines of stuff, but we're only interested in the last line, which should be something like '''program number service''', if program is Skype.exe, you can '''change the port''' it listens on; if <service> is not N/A then proceed to the next step
# Type '''net stop service''', replace '''service''' with the one displayed after executing the command above (it shouldn't have any spaces).
## You should see something like "The xxxx service was stopped successfully", this means that you've got rid of the service (probably IIS) that was using port 80 (and thus making you unable to access Uniform Server);
'''''[[#top | Top]]'''''
=== port 80 kill process XP Home ===
XP home does not support the tasklist command. A better alternative for both xp pro and home is to use:
'''procexp.exe from Sysinternals'''
Microsoft acquired Sysinternals in July, 2006 free download: [http://www.microsoft.com/technet/sysinternals/utilities/ProcessExplorer.mspx Process Explorer for Windows]
It is a single file and well worth popping on your memory stick.
'''Using'''
The easiest way to use this tool is to obtain a list of what is running on port 80 using:
# Start the Command Prompt and then type netstat -ano | find "LISTENING" | find ":80"
## You'll see a bunch of stuff like "'''TCP x.x.x.x:80 x.x.x.x:0 LISTENING number'''", what we're interested in here is '''number''' the '''PID'''
# Now run procexp.exe look down the list of PID's and find the ones from the above step. You now have the process name and possibly a description.
# Right click on the file name and select '''Kill Process''' repeat for all the above. Now start UniServer you will find it now works.
All you need to do now is decide what you want to do with the offending programs (they will restart next time you reboot) either delete or change the listening ports.
'''''[[#top | Top]]'''''
=== Unistall IIS ===
'''XP Pro''' comes with '''Windows IIS''' (Windows Internet Information Server) pre-installed, the following details how to remove it.<br>
Note: '''XP Home''' does not have IIS installed hence not a problem.
To uninstall IIS using Add or Remove a Windows Component in Control Panel
# From the '''Start''' menu, click '''Control Panel'''.
# Double-click '''Add or Remove Programs'''.
# Click '''Add/Remove Windows Components'''.
# In the '''Components''' list click the '''Application Server check bo'''x.
# Click '''Next'''.
# Click '''Close''' when un-installation of IIS is complete.
''Alternative method''
'''To uninstall IIS using the Configure Your Server Wizard'''
# From the '''Start''' menu, click '''Manage Your Server'''.
# Under '''Managing Your Server Roles''', click '''Add or remove a role'''.
# Read the preliminary steps in the '''Configure Your Server Wizard''' and click '''Next'''.
# Under Server Role, click Application server (IIS, ASP.NET) and then click Next.
# In the '''Role Removal Configuration''' dialog, check the '''Remove the application server''' role check box.
# Complete the wizard, and then click '''Finish'''.
'''''[[#top | Top]]'''''
=== Disable IIS ===
If you must have IIS on your machine you have two alternatives as follows:
You can disable IIS by using the Internet Information Services applet in the Administrative tools area of Control panel.
# Select the '''Default Web Site''' element
# Right click it
# Now click '''Stop'''.
=== Move IIS to another port ===
If you want to run IIS on another port check out this page [[Reverse Proxy Server 2: IIS back-end server | '''IIS back-end server''']]
This solutions allows you to use ASP and other applications best suited to IIS
=== Move UniServer to another port ===
Alternatively if you want to run UniServer on another port check out this page [[5.0-Nano: Multi-Servers | '''Multi-Servers''']]
'''''[[#top | Top]]'''''
=== Skype ===
Skype is a little piece of software that lets you make free telephone calls anywhere in the world to another Skype user.
They like Uniserver have their own problems with firewalls check out this link. Skype may and does use port 80 this conflicts with Uniserver however it is quite an obliging piece of software in that it can share port 80 or be moved on.
'''Shared port'''
I have not confirmed this works but worth a try:
# Stop Uniserver
# Stop Skype
# '''Start''' Uniserver
# Then '''start''' Skype
If this solution works let me know! However the preferred solution is that recommended by Olajide:
'''Move it on'''
Move Skype to another port
# '''Skype''' > '''Tools''' > '''Options''' > '''Connections'''
# '''Change''' the port to something like '''85(incoming)'''. Check that both Uniserver and Skype are happy or try another port.
PS I trust you have killed off... [[#Unistall IIS | IIS]] that's another story.
'''''[[#top | Top]]'''''
== Server not accessible from Internet ==
'''Q)''' I have tried every thing but my servers are not accessible from the Internet.
'''A)''' There can be any number of reasons why your server is not accessible from the Internet. The path to your server is not direct a typical access follows this sequence
# A user types into their browser a URL to access a page on your server.
# The domain part of the URL needs to be converted to an IP address that points to your server.
# A browser sends a request to a DNS server to obtain this IP address
# A browser uses the returned IP address to send a page request to your server
# If your server is connected to the Internet via a router the request is routed to your internal network address on port 80.
# This may be intercepted by a firewall and rejected if it has not been configured to allow access.
# Your server uses file .htacces to check allowed IP access if you have not configured this file the request will be rejected (default is to allow only local access).
# Assuming you have enabled external access in file .htaccess the page is served.
# This may be intercepted by a firewall and rejected if it has not been configured to allow Apache to act as a server.
# The above assumes your ISP does not block the ports.
External access requires passing all ten steps resolving an access failure requires pinpointing the cause. Uniform Server contains diagnostics that breaks the above chain making it easier to isolate the cause.
'''''[[#top | Top]]'''''
=== Server Status ===
With the servers running run Server Status from UniTray note what is displayed for the first two entries.
One of two results are displayed for each entry as follows:
* '''''Your Internet IP Address'':''' IP address displayed or Not connected or error
* '''''Accessible from Internet'':''' YES or NO
==== IP address ====
Your IP address is obtained from an external page. If you can surf the Internet from a browser you should see an IP address. Should an IP not be displayed it could be because the external server is down!
==== Accessibility ====
Accessibility test uses the above IP address to access your server it removes the dependence on a DN server. In addition it reads a page on your server UniServer\home\access\www\'''index.html'''
The folder is not protected by an .htaccess file hence removes any issues associated with .htaccess files.
Failing this test reduces to one or more of the following causes
* Port forwarding is not enabled in router
* Firewall blocking server
* ISP blocking port
Passing this test indicates you may have not enabled external access in file .htaccess.
A quick test is to enter your IP address into a browser e.g <nowiki>http:</nowiki>//999.163.178.100 your home page should be displayed.
If not check out this page to [[5.0-Nano: Install and Run#Put Server on-line | '''put your servers on-line''']].
If server is accessible using your IP address and still cannot be accessed using your domain name indicates an issue at your DNS provider is the IP setting correct.
'''''[[#top | Top]]'''''
== HOSTS File ==
For details see page [[New Users: Quick hosts file | '''New Users Quick hosts file''']]
The hosts file is located in the system folder. The path may be different depending on your setup, these paths are for typical default installations.
{|style="border:1px solid #444444"
|-
|'''c:\windows\~system32\drivers\etc'''|| — Windows Vista
|-
|'''c:\winnt\system32\drivers\etc\hosts'''|| — Windows NT/2000/XP Pro
|-
|'''c:\windows\system32\drivers\etc\hosts'''|| — Windows XP Home
|}
Should contain the following as a minimum:
{| cellpadding="4" cellspacing="1" style="background:#000000;"
|style="background:#f5f5f5;"|
<pre style="border:0;margin:0;padding:0">
127.0.0.1 localhost    # loop back address
127.0.0.1 localhost:80 # loop back address
</pre>
|}
=== Cannot access server using localhost but 127.0.0.1 works ===
'''Q)''' I cannot access server using '''localhost''' however <nowiki>http:</nowiki>//127.0.0.1 works
'''A''') Check the '''hosts''' file contains these two entries:
*  127.0.0.1 localhost
* 127.0.0.1 localhost:80
'''''[[#top | Top]]'''''
==== Error message localhost/apanel has no data ====
'''Q)''' I type '''<nowiki>http://localhost/apanel</nowiki>''' it fails with error message localhost/apanel '''has no data'''.
'''A)''' Try '''<nowiki>http://127.0.0.1/apanel/</nowiki>''' as an alternative. If this works you most likely have entries in the “hosts” file that are specific to IPv6 look for entries similar to these:
<pre>
:. localhost
or
:. 127.0.0.1
</pre>
Comment them out by adding a # (hash) at the beginning of each line for example:
<pre>
# :. localhost
or
# :. 127.0.0.1
</pre>
The "hosts" file should contain only these lines for IP 127.0.0.1
* '''127.0.0.1 localhost'''
* '''127.0.0.1 localhost:80'''
'''''[[#top | Top]]'''''
==== Localhost does not work on another PC ====
Trying to run servers on another PC and localhost does not work, see above.
I have moved my servers to a different port and localhost:81 on another PC does not work.
You require an entry in the hosts file that looks like this:
{| cellpadding="4" cellspacing="1" style="background:#000000;"
|style="background:#f5f5f5;"|
<pre style="border:0;margin:0;padding:0">
127.0.0.1 localhost:81 # loop back address
</pre>
|}
Alternatively use '''<nowiki>http:</nowiki>//127.0.0.1:81''' to access the servers.
'''''[[#top | Top]]'''''
== VHOSTS ==
=== VHOSTS Not working on another PC ===
'''Q''' I have several virtual hosts set using Apanel, they do not work on another PC.
'''A)''' Add corresponding entries in that PC's '''hosts file''' 
'''''[[#top | Top]]'''''
== LAN ==
=== Cannot access server from another PC ===
'''Q)''' Other users cannot access my server from their PC's on the same LAN or wireless network. My server is working fine locally.
'''A)''' Check you have enabled external access in .htaccess.
* On the machine running the server
* Run a command prompt and type '''ipconfig /all'''
* Look for Host Name e.g '''fred123''' this should be unique for each machine.
* Alternatively look for IP Address e.g '''192.168.1.6'''
On other machines now try the following:
* Type the following into a browser '''<nowiki>http:</nowiki>//fred123/'''
* Alternatively type the following into a browser '''<nowiki>http:</nowiki>//192.168.1.6/'''
'''''[[#top | Top]]'''''


== Vista ==
== Vista ==
Line 8: Line 265:
* Solution: Download the '''.exe''' files these are 7Z self-extracting archives
* Solution: Download the '''.exe''' files these are 7Z self-extracting archives


'''''[[#top | Top]]'''''
== PHP Scripts ==
== PHP Scripts ==
* Problem: Some third party PHP scripts fail to install with '''development php.ini'''
* Problem: Some third party PHP scripts fail to install with '''development php.ini'''

Revision as of 19:41, 11 September 2009

 

Known issues and problems

This page contains known issues and problems, where applicable offers solutions.

Servers not starting

Q) Apache and or MySQL servers will not start why?

A) If port 80 is being used by another service or server Uniform Server will not start. Before starting UniServer make sure you do not have another service running on Port 80.

Run Server Status from UniTray: Check ports are free to use.

If they are in use try the following solutions:

Top

port 80 kill process XP Pro

You can kill the processes that use port 80 on XP Pro as follows:

  1. Start the Command Prompt and then type netstat -ano | find "LISTENING" | find ":80"
    1. You'll see a bunch of stuff like "TCP x.x.x.x:80 x.x.x.x:0 LISTENING number", what we're interested in here is number, if there are more than one (which normally shouldn't happen), repeat the steps below for each one
  2. Type tasklist /SVC /FI "PID number", replace number with the one you saw after executing the first command.
    1. You'll see 3 lines of stuff, but we're only interested in the last line, which should be something like program number service, if program is Skype.exe, you can change the port it listens on; if <service> is not N/A then proceed to the next step
  3. Type net stop service, replace service with the one displayed after executing the command above (it shouldn't have any spaces).
    1. You should see something like "The xxxx service was stopped successfully", this means that you've got rid of the service (probably IIS) that was using port 80 (and thus making you unable to access Uniform Server);

Top

port 80 kill process XP Home

XP home does not support the tasklist command. A better alternative for both xp pro and home is to use:

procexp.exe from Sysinternals

Microsoft acquired Sysinternals in July, 2006 free download: Process Explorer for Windows

It is a single file and well worth popping on your memory stick.

Using

The easiest way to use this tool is to obtain a list of what is running on port 80 using:

  1. Start the Command Prompt and then type netstat -ano | find "LISTENING" | find ":80"
    1. You'll see a bunch of stuff like "TCP x.x.x.x:80 x.x.x.x:0 LISTENING number", what we're interested in here is number the PID
  2. Now run procexp.exe look down the list of PID's and find the ones from the above step. You now have the process name and possibly a description.
  3. Right click on the file name and select Kill Process repeat for all the above. Now start UniServer you will find it now works.

All you need to do now is decide what you want to do with the offending programs (they will restart next time you reboot) either delete or change the listening ports.

Top

Unistall IIS

XP Pro comes with Windows IIS (Windows Internet Information Server) pre-installed, the following details how to remove it.
Note: XP Home does not have IIS installed hence not a problem.

To uninstall IIS using Add or Remove a Windows Component in Control Panel

  1. From the Start menu, click Control Panel.
  2. Double-click Add or Remove Programs.
  3. Click Add/Remove Windows Components.
  4. In the Components list click the Application Server check box.
  5. Click Next.
  6. Click Close when un-installation of IIS is complete.

Alternative method

To uninstall IIS using the Configure Your Server Wizard

  1. From the Start menu, click Manage Your Server.
  2. Under Managing Your Server Roles, click Add or remove a role.
  3. Read the preliminary steps in the Configure Your Server Wizard and click Next.
  4. Under Server Role, click Application server (IIS, ASP.NET) and then click Next.
  5. In the Role Removal Configuration dialog, check the Remove the application server role check box.
  6. Complete the wizard, and then click Finish.

Top

Disable IIS

If you must have IIS on your machine you have two alternatives as follows:

You can disable IIS by using the Internet Information Services applet in the Administrative tools area of Control panel.

  1. Select the Default Web Site element
  2. Right click it
  3. Now click Stop.

Move IIS to another port

If you want to run IIS on another port check out this page IIS back-end server

This solutions allows you to use ASP and other applications best suited to IIS

Move UniServer to another port

Alternatively if you want to run UniServer on another port check out this page Multi-Servers

Top

Skype

Skype is a little piece of software that lets you make free telephone calls anywhere in the world to another Skype user. They like Uniserver have their own problems with firewalls check out this link. Skype may and does use port 80 this conflicts with Uniserver however it is quite an obliging piece of software in that it can share port 80 or be moved on.

Shared port

I have not confirmed this works but worth a try:

  1. Stop Uniserver
  2. Stop Skype
  3. Start Uniserver
  4. Then start Skype

If this solution works let me know! However the preferred solution is that recommended by Olajide:

Move it on

Move Skype to another port

  1. Skype > Tools > Options > Connections
  2. Change the port to something like 85(incoming). Check that both Uniserver and Skype are happy or try another port.

PS I trust you have killed off... IIS that's another story.

Top

Server not accessible from Internet

Q) I have tried every thing but my servers are not accessible from the Internet.

A) There can be any number of reasons why your server is not accessible from the Internet. The path to your server is not direct a typical access follows this sequence

  1. A user types into their browser a URL to access a page on your server.
  2. The domain part of the URL needs to be converted to an IP address that points to your server.
  3. A browser sends a request to a DNS server to obtain this IP address
  4. A browser uses the returned IP address to send a page request to your server
  5. If your server is connected to the Internet via a router the request is routed to your internal network address on port 80.
  6. This may be intercepted by a firewall and rejected if it has not been configured to allow access.
  7. Your server uses file .htacces to check allowed IP access if you have not configured this file the request will be rejected (default is to allow only local access).
  8. Assuming you have enabled external access in file .htaccess the page is served.
  9. This may be intercepted by a firewall and rejected if it has not been configured to allow Apache to act as a server.
  10. The above assumes your ISP does not block the ports.

External access requires passing all ten steps resolving an access failure requires pinpointing the cause. Uniform Server contains diagnostics that breaks the above chain making it easier to isolate the cause.

Top

Server Status

With the servers running run Server Status from UniTray note what is displayed for the first two entries.

One of two results are displayed for each entry as follows:

  • Your Internet IP Address: IP address displayed or Not connected or error
  • Accessible from Internet: YES or NO

IP address

Your IP address is obtained from an external page. If you can surf the Internet from a browser you should see an IP address. Should an IP not be displayed it could be because the external server is down!

Accessibility

Accessibility test uses the above IP address to access your server it removes the dependence on a DN server. In addition it reads a page on your server UniServer\home\access\www\index.html

The folder is not protected by an .htaccess file hence removes any issues associated with .htaccess files.

Failing this test reduces to one or more of the following causes

  • Port forwarding is not enabled in router
  • Firewall blocking server
  • ISP blocking port

Passing this test indicates you may have not enabled external access in file .htaccess.

A quick test is to enter your IP address into a browser e.g http://999.163.178.100 your home page should be displayed.

If not check out this page to put your servers on-line.

If server is accessible using your IP address and still cannot be accessed using your domain name indicates an issue at your DNS provider is the IP setting correct.

Top

HOSTS File

For details see page New Users Quick hosts file

The hosts file is located in the system folder. The path may be different depending on your setup, these paths are for typical default installations.

c:\windows\~system32\drivers\etc — Windows Vista
c:\winnt\system32\drivers\etc\hosts — Windows NT/2000/XP Pro
c:\windows\system32\drivers\etc\hosts — Windows XP Home

Should contain the following as a minimum: 

127.0.0.1 localhost    # loop back address
127.0.0.1 localhost:80 # loop back address

Cannot access server using localhost but 127.0.0.1 works

Q) I cannot access server using localhost however http://127.0.0.1 works

A) Check the hosts file contains these two entries:

  • 127.0.0.1 localhost
  • 127.0.0.1 localhost:80

Top

Error message localhost/apanel has no data

Q) I type http://localhost/apanel it fails with error message localhost/apanel has no data.

A) Try http://127.0.0.1/apanel/ as an alternative. If this works you most likely have entries in the “hosts” file that are specific to IPv6 look for entries similar to these: 

:. localhost
or
:. 127.0.0.1

Comment them out by adding a # (hash) at the beginning of each line for example: 

# :. localhost
or
# :. 127.0.0.1

The "hosts" file should contain only these lines for IP 127.0.0.1

  • 127.0.0.1 localhost
  • 127.0.0.1 localhost:80

Top

Localhost does not work on another PC

Trying to run servers on another PC and localhost does not work, see above.

I have moved my servers to a different port and localhost:81 on another PC does not work.

You require an entry in the hosts file that looks like this: 

127.0.0.1 localhost:81 # loop back address

Alternatively use http://127.0.0.1:81 to access the servers.

Top

VHOSTS

VHOSTS Not working on another PC

Q I have several virtual hosts set using Apanel, they do not work on another PC.

A) Add corresponding entries in that PC's hosts file

Top

LAN

Cannot access server from another PC

Q) Other users cannot access my server from their PC's on the same LAN or wireless network. My server is working fine locally.

A) Check you have enabled external access in .htaccess.

  • On the machine running the server
  • Run a command prompt and type ipconfig /all
  • Look for Host Name e.g fred123 this should be unique for each machine.
  • Alternatively look for IP Address e.g 192.168.1.6

On other machines now try the following:

  • Type the following into a browser http://fred123/
  • Alternatively type the following into a browser http://192.168.1.6/

Top

Vista

  • Problem: Earlier versions of Vista have problems extracting .zip files
  • Solution: Download the .exe files these are 7Z self-extracting archives

Top

PHP Scripts

  • Problem: Some third party PHP scripts fail to install with development php.ini
  • Solution: Before installing third party scripts use UniTray and switch to production php.ini (Default after extraction).
  • For the new php.ini file to be picked up remember to restart server.

Top

Retrieved from "https://wiki.uniformserver.com/index.php?title=5.0-Nano:_Known_Issues&oldid=3870"