CensorNet

FAQ Section 2 - Post Installation

Questions

Q2.1 The CensorNet is installed, I can ping things, but we just get Page Not Found.
Q2.2 I can't log into the CensorNet's web administration pages.

Q2.1 The CensorNet is installed, I can ping things, but we just get Page Not Found.

A2.1 There are a number of reasons that this can be so, and they'll all be listed below.

Unless you are running CN3.2r3 or later, there is a problem during installation which leaves the CensorNet in an uncertain state regarding whether it's in Bridge mode or Router and Firewall mode. The solution is to log into the command line, run the setup program, go to Network Configuration and choose Set Router/Bridge mode. One of the options will currently be configured, select the alternate one and allow the CensorNet to reconfigure itself. Once it's finished, choose the same option again and go back to the mode that you require. After its reconfigured itself again, things may work as you require.
The next most problematic issue is the configuration of the DNS. Have you entered the name servers' IP addresses correctly? Try and ping something external (on the Internet) by name (from the CensorNet's command line), and see if its IP address is resolved. The IP address will appear in brackets when the system tells you that it's attempting to ping said address. If it fails to resolve the name to an IP, then that will be your problem, and you need to find out why. Check the CensorNet's DNS configuration from the setup program, and if you're sure the values are correct, you will have to check with your ISP as to why they aren't resolving names.
Have you probed your LAN for MAC addresses? One of the things you should have done is to probe your LAN so that the CensorNet can build up a list of workstations on your LAN. You need to ensure all your workstations are on. Any that are off during the probe will not, of course, be picked up. To run the probe, run the setup program as described before, go to the System Maintenance menu, and from there choose Probe LAN for MAC Addresses. Having done this, you can proceed to the next point.
Log into the CensorNet's web interface (see A2.2 for reasons why you might not be able to do this) and go to the Workstations tab. From there choose Access Control from the drop down menu. Ensure the workstation you're having the problem with has either Allow Web or Allow Web and Other as their profile. Of course, if you've defined your own profile for the station, it will need to have an element of Allow Web in it at the time you're trying to surf. If it does, check the CensorNet's clock by typing date at its command line.
Check the status of the services. If you're in the web interface go to the Home tab (if you're not already) and look at the list of services. For things to work, you need Dansguardian (dg), Squid and Postgresql (pg) to be running. If any of these are shown in red, you have a problem. Both Dansguardian and Squid rely on Postgresql so you should always try and restart that first. You can try and start the services by clicking on the red lights. If that fails, you'll need to log in as root at the CensorNet's command line. Start/Stop scripts can be found in /etc/init.d. If you know enough Linux, try and fix it, otherwise post a report to the forum and we'll assist.

Q2.2 I can't log into the CensorNet's web administration pages.

A2.2 This can be caused by a number of reasons as well, and we'll list these point by point below.

By far and away the most common cause for this is a misconfigured browser. Almost certainly, you've configured your Internet Explorer to use the CensorNet on port 8080, you've ticked the tick box to say "Use for all protocols" and you've ticked the "Do not use proxy for local addresses." Unfortunately, the latter tick box mostly doesn't work. What you need to do is to click the "Advanced" button. When you do this, you'll see the list of all the protocols, all set to use the CensorNet. At the bottom of the window is a box which reads "Do not use Proxy for ". You need to add the CensorNet's IP address in that box too.
Have you allowed the workstation you're working from access to the Admin pages? If not, go to a workstation which can reach the pages, log in, go to the Workstations tab and then select Admin Area Access from the drop down menu. Find your workstation and click allow and then update.
If you really can't find a workstation with access to the web interface, then log into the CensorNet's command line. Run setup. Go to the System Maintenance menu. Choose Reset Admin Area Access. After you do this, that part of the system will be back in its "just after install" state. All workstations are listed as "not allowed" and so, conversely, every workstation is allowed, just so that you can get in. Now, you should be able to get into the Web Admin pages from any workstation. If you still can't..
It is likely that the Apache process has died on the CensorNet, and as a consequence, the machine simply can't serve you the Admin pages. You could reboot the CensorNet, which might fix things, but as a first attempt, log into the CensorNet as root, and type /etc/init.d/apache start which should either fix things, or give you an error message giving information as to what the problem is. If you don't understand what it means, post a request on the forum - including a copy of the error message you received.