Cannot contect to apache through wrt54g

However, it is possible that there's something wrong on your end and we'll work through those possibilities below.

1. Try loading the URL again by pressing F5 on your keyboard, or by clicking the refresh/reload button.
   
   While the 502 Bad Gateway error is usually indicating a networking error outside of your control, it could be extremely temporary. Trying the page again will often be successful.
2. Start a new browser session by closing all open browser windows and then opening a new one. Then try opening the webpage again.
   
   It's possible that the 502 error you received was due to an issue on your computer that occurred sometime during this use of your browser. A simple restart of the browser program itself could solve the problem.
3. Clear your browser's cache. Outdated or corrupted files that are being stored by your browser could be causing 502 Bad Gateway issues.
   
   Removing those cached files and trying the page again will solve the problem if this is the cause.
4. Delete your browser's cookies. For similar reasons as mentioned above with cached files, clearing stored cookies could fix a 502 error.
   
   Note: If you'd rather not clear all of your cookies, you could first try removing only those cookies related to the site you're getting the 502 error on. It's best to remove them all but it won't hurt to try the clearly applicable one(s) first.
5. Start your browser in Safe Mode. Running a browser in Safe Mode means to run it with default settings and without add-ons or extensions, including toolbars.
   
   If the 502 error no longer appears when running your browser in Safe Mode, you know that some browser extension or setting is the cause of the problem. Return your browser settings to default and/or selectively disable browser extensions to find the root cause and permanently fix the problem.
   
   Note: A browser's Safe Mode is similar in idea to the Safe Mode in Windows but it is not the same thing. You do not need to start Windows in Safe Mode to run any browser in its particular "Safe Mode."
6. Try another browser. Popular browsers include Firefox, Chrome, Internet Explorer, andSafari, among others.
   
   If an alternative browser doesn't produce a 502 Bad Gateway error, you now know that your original browser is the source of the problem. Assuming you've followed the above troubleshooting advice, now would be the time to reinstall your browser and see if that corrects the problem.
7. Download Software Update 1 for Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 1 if you have MS Forefront TMG SP1 installed and receive a Error Code: 502 Proxy Error. The network logon failed. (1790) or similar message when accessing a web page.
   
   Important: This is not a common solution to 502 Proxy Error messages and only applies in this particular situation. Forefront TMG 2010 is a business software package and you would know if you have it installed.
8. Restart your computer. Some temporary issues with your computer and how it's connecting to your network could be causing 502 errors, especially if you're seeing the error on more than one website. In these cases, a restart would help.
9. Restart your networking equipment. Issues with your modem, router, switches, or other networking devices could be causing 502 Bad Gateway or other 502 errors. A simple restart of these devices could help.
   
   Tip: The order you turn off these devices isn't particularly important, but be sure to turn them back on from the outside in. In other words, turn on the outermost hardware on the network first (usually your modem), followed by the device it's connected to (usually your router). Next would be any switch or other device between the router and your computer.
10. Change your DNS servers, either on your router or on your computer or device. Some Bad Gateway errors are caused by temporary issues with DNS servers.
    
    Note: Unless you've previously changed them, the DNS servers you have configured right now are probably the ones automatically assigned by your ISP. Fortunately, a number of other DNS servers are available for your use that you can choose from. See my Free & Public DNS Servers list for your options.
11. Contacting the website directly might also be a good idea. Chances are, assuming they're at fault, the website administrators are already working on correcting the cause of the 502 Bad Gateway error but feel free to let them know about it.
    
    See my Website Contact Information page for a list of contacts for popular websites. Most websites have social networking accounts they use to help support their services. Some even have telephone and email contacts.
    
    Tip: If you suspect that a website is down for everyone, especially a popular one, checking Twitter for chatter about the outage is often very helpful. The best way to do this is to search for #websitedown on Twitter, as in #cnndown or #instagramdown.
12. Contact your Internet Service Provider. If your browser, computer, and network is working, and the website reports that the page or site is working for them, the 502 Bad Gateway issue could be caused by a network issue that your ISP is responsible for.
    
    Tip: See How To Talk To Tech Support for tips on talking to your ISP about this problem.
13. Come back later. At this point in your troubleshooting, the 502 Bad Gateway error message is almost certainly an issue with either your ISP or with the web site's network - one of the two parties may have even confirmed that for you if you contacted them directly.
    
    Either way, you're not the only one with seeing the 502 error and you'll need to wait until the problem is solved for you.

Errors Like 502 Bad Gateway

The following error messages are related to the 502 Bad Gateway error:
500 Internal Server Error ' 503 Service Unavailable ' 504 Gateway Timeout
A number of client-side HTTP status codes also exist, like the very common 404 Not Found error, among many others: List of HTTP Status Code Errors.

Generally, a 502 error is not something you can fix. It means that one or more of the servers that fulfill your request for a web page aren't sending back what's expected. (It's quite typical for a web site to grab data from other places to render the page you are looking at. The main text usually comes from the site you are looking at, but a lot of the times, the pictures, video, comments section, etc., might be hosted on another machine altogether. The ads placed on web pages typically come from outside servers.)

If this is the only web site on which you are getting a 502 error, it probably is the site. However, I was able to go to http://www.quotev.com/ (using FIrefox 19.0.2 and Chrome Version 25.0.1364.172 m) with no issues, which makes me wonder. If you are getting the error when visiting a lot of sites, it's probably time to do some more digging on your end. Have you tried power cycling the router that serves the Internet at your place? It's possible that the site has moved to a new server and the router has some of the old web site IPs in it's routing table. That is, it might not be your laptop, but in the router or further upstream toward the web site.

Make sure that you are using all capital letters in the registration number. You can initiate a tech support ticket here:

http://support.topics-ent.com/cgi-bin/support.pl

If you really need a phone number, call: USA 425-656-3621

Retry the web page by clicking the refresh/reload button or trying the URL from the address bar again. Even though the 500 Internal Server Error is reporting a general error on the web site's servers and not your computer, the server error may only be temporary. Trying the page again will often be successful. http://moritsolutions.com/

Hi liverpool97.
Let me explain you about the Proxy servers.
In Computer Networks, a Proxy Server is a Server (a Computer system or an application program) that acts as an intermediary for requests from clients seeking resources from other servers.
A client connects to the proxy server, requesting some service, such as a file, connection, web page, or other resource, available from a different server.
The proxy server evaluates the request according to its filtering rules.
For example, it may filter traffic by IP address or protocol. If the request is validated by the filter, the proxy provides the resource by connecting to the relevant server and requesting the service on behalf of the client.
A proxy server may optionally alter the client's request or the server's response, and sometimes it may serve the request without contacting the specified server.
In this case, it 'caches' responses from the remote server, and returns subsequent requests for the same content directly.
Hope this helps.
Please let me know if you need further information about the Proxy servers.
I'll be glad to assist you.

To access "localhost" you must have a web server ( IIS or Apache - IIS is the simplest and is found in add/remove programs, Windows components usually) running on the PC that Joomla is installed on. You must also use http://localhost for it to work. Localhost means you are only doing a loopback to your own pc for testing purposes. By default most web servers run on port 80 if the port is changed then you must use "http://localhost:port". Depending on how your network is set up - If you have a router or firewall you may also have to "open" or do a port forward to port 80 for the software to see the server holding the Joomla pages and also allow internet access as a server. First try the default web page the server has usually default.htm or index.htm as http://localhost/default.htm etc, if it loads then you know localhost is functioning, then try the Joomla page you want to see using it in place of default.htm. If no page loads at the start - then check your Apache(Xampp) configuration file to be sure it is set up and working properly - if I recall it is hhtp.conf open it with notepad to configure and save as "all files" not text. You might also check your Joomla configuration options as well to be sure the correct port and location are used for serving pages.

If you are running Windows XP Professional on your computer you can install Microsoft's web server, Internet Information Server 5.1 (IIS) for free from the Windows XP Pro installation CD and configure it to run on your system by following the instructions below: -
1. Place the Windows XP Professional CD-Rom into your CD-Rom Drive.

2. Open 'Add/Remove Windows Components' found in 'Add/Remove Programs' in the 'Control Panel'.

3. Place a tick in the check box for 'Internet Information Services (IIS)' leaving all the default installation settings intact.

4. Once IIS is installed on your machine you can view your home page in a web browser by typing 'http://localhost' (you can substitute 'localhost' for the name of your computer) into the address bar of your web browser. If you have not placed your web site into the default directory you should now be looking at the IIS documentation.

5. If you are not sure of the name of your computer right-click on the 'My Computer' icon on your desktop, select 'Properties' from the shortcut menu, and click on the 'Computer Name' tab.

6. Your default web directory to place your web site in is 'C:\Inetpub\wwwroot', but if you don't want to over write the IIS documentation found in this directory you can set up your own virtual directory through the 'Internet Information Services' console.

7. The 'Internet Information Services' console can be found in the 'Administration Tools' in the 'Control Panel' under 'Performance and Maintenance', if you do not have the control panel in Classic View.


8. Double-click on the 'Internet Information Services' icon.


8. Once the 'Internet Information Services' console is open you will see any IIS web services you have running on your machine including the SMTP server and FTP server, if you chose to install them with IIS.

9. To add a new virtual directory right click on 'Default Web Site' and select 'New', followed by 'Virtual Directory', from the drop down list.



7. Next you will see the 'Virtual Directory Creation Wizard' from the first screen click the 'next' button.

9. You will then be asked to type in an 'Alias' by which you will access the virtual directory from your web browser (this is the name you will type into your web browser after 'localhost' to view any web pages you place in the directory).

10. Next you will see a 'Browse...' button, click on this to select the directory your web site pages are in on your computer, after which click on the 'next' button to continue.

11. On the final part of the wizard you will see a series of boxes, if you are not worried about security then select them all, if you are and want to run ASP scripts then check the first two, followed by the 'next' button.

12. Once the virtual directory is created you can view the web pages in the folder by typing 'http://localhost/aliasName' (where 'aliasName' is, place the alias you called the virtual directory) into the address bar of your web browser (you can substitute 'localhost' for the name of your computer if you wish).

I am using this http://www.tucktail.com/ domain and hosting for all my sites ,there is no problem ,also i spend just $1.99 per year .

Does that mean that you got a answer to it?. If not you may have a hijacker running. Download a free hijacker sweeper program and run it. that should cure the problem.

Dear Rajiv

First make sure that your Apache server is running properly.
For this type http://localhost and see the result.

If you want to test PHP you can create a php test file by yourself.

Goto the www folder in apache director. create a file , name it anything.php. Edit the file and simply write "phpinfo()" without quotes . check the output.

It means that your apache server is fully capable of PHP scripting.

Cheers, Parveen