paulsrichards.com Report : Visit Site

Technical data of the paulsrichards.com

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host paulsrichards.com. Currently, hosted in United Kingdom and its service provider is DigitalOcean London .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called Apache/2.4.7 (Ubuntu) containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

paul richards just another wordpress site menu skip to content home timing chain cover to engine block water coolant leak chrysler voyager 3.3 v6 (2000) timing chain cover to engine block water coolant leak. as well as the usual coolant water leaks associated with my chrysler voyager 3.3 v6 (2000) e.g. radiator, water pump, hoses etc. i encountered a slight and intermittent coolant leak between the timing chain cover and the left side of the engine block . the vehicle which i’ve had from new, has now over 102000 miles on the clock. so i guess this mileage and age was a contributory factor. below is a step by step guide of how i replaced the timing chain cover gasket and the failed “o” rings on the water galleries between the timing chain cover and engine block. you might find this photo guide useful if you decide to tackle the job yourself. i’m sure you can do the job without removing the bonnet and wiper box, but for the time it takes it makes the rest of the job a lot more accessible plus it gives a bit more light on the subject. 1. disconnect battery and remove bonnet and wiper box. see this link for wiper box removal http://www.paulsrichards.com/2008/06/13/changing-the-spark-plugs-on-a-chrysler-voyager-v6/ 2. the vehicle runs on lpg, so turn of the gas supply at the tank. 3. drain radiator and remove lpg control valve. 4. with the hoses removed you can just see the residue of the coolant leak between the timing cover and engine block. 5. raise the vehicle with suitable jack and support with axle stands. remove right front wheel, the plastic wing protector and the plastic crankshaft pulley protector. 6. remove the serpentine belt using a combination spanner on the bolt head of the belt tensioner pulley. do this by reaching up from the underside of the vehicle. you might need to use a ring spanner on the open ended jaw of the combination spanner for extra leverage against the spring tension. pull the belt from the crankshaft pulley. 7. remove water pump and hoses. 8. slacken the crankshaft pulley bolt (easier with an air wrench) use a puller to remove the pulley. it will be tight all the way off. 9. remove the idler pulley, unbolt the aircon pump and cable tie to one side. do not remove any pipes from the aircon pump! 10. drain the engine oil and remove the sump and pick up pipe. removal of a stabiliser bracket on the side of the engine block may be required to remove the starter ring gear cover. 11. suitably support the engine for the removal of the right side engine mounting. 12. remove the engine mounting. first remove the vertical and horizontal bolt to the engine mounting bracket then remove the 3 bolts fixing the rubber mounting bracket to the chassis. 13. remove the 3 bolts holding engine mounting plate to the timing chain cover (left in photo) 14. unplug the camshaft sprocket positioning sensor multi plug. 15. remove the 8 timing chain cover bolts and ease the cover over end of crankshaft to remove. 16. check timing chain cover for faults. note on this photo the two water gallery “o” rings are damaged and are the cause of the coolant leak. the lower left hand port on the casing has an “o” ring for the oil gallery. 17. clean the timing chain cover mating surface with a scraper and emery cloth, paying particular attention to the “o” ring seats which are very close to the edge of the casing. 18. clean the engine block mating surface and check timing chain and sprockets for serviceability. 19. fit 3 new “o” rings and gasket to the timing chain cover using a suitable gasket sealant. 20. refit timing chain cover ensuring “o” rings do not drop out of position. rotate if necessary the two flats on the oil pump drive so they align with the two flats on the crankshaft. 21. refit sump with new gasket and and oil pick up pipe “o” ring. 22. refit crankshaft pulley using a long 10mm bolt and nut to jack the pulley back on the crankshaft. it will be a tight fit all the way. 23. rebuild the remainder of the components. it might be worth replacing the serpentine drive belt at this stage. 24. parts used: timing chain cover gasket and “o” rings, not expensive sump gasket set, quite expensive. part codes: b0000k04621958 – sealing gasket (timing chain cover) b00k04483444ab – ring (timing chain cover) b0000k04483443 – sealing gasket (timing chain cover) b00k05241062ab – seal kit (sump) this entry was posted in cars and tagged cars , voyager on august 3, 2014 by steve richards . how to install backup-manager on fedora and configure amazon s3 you may of noticed that installing backup-manager on fedora (i’m using oldish version 9) isn’t that straight forward, particularly if you want to back up to amazon s3. it took my a bit of messing around on how to do it so i thought it was worth sharing how i did it. note that if you wish not to use amazon s3 once its installed your all done. installing backup-manager download the rpm to your server $ wget ftp://ftp.pbone.net/mirror/archive.fedoraproject.org/fedora/linux/updates/9/ppc.newkey/backup-manager-0.7.8-1.fc9.noarch.rpm if the link gets broken at some point there is a load more here http://rpm.pbone.net/index.php3/stat/4/idpl/13697398/dir/fedora_9/com/backup-manager-0.7.8-1.fc9.noarch.rpm.html . if you use a different fedora version you can find the correct rpm here. you can install this now with $ rpm -ivh backup-manager-0.7.8-1.fc9.noarch.rpm if you dont need amazon s3 to work your all done at this point. amazon s3 if you run it at this point your get the error message: the upload transfer "s3" failed. you must install 2 more packages that it doesn’t tell you about. do the following under root $ yum search perl-file-slurp $ yum install perl-file-slurp.noarch now one more package $ yum search perl-net-amazon-s3 $ yum install perl-net-amazon-s3.noarch and now you can configure your conf: nano /etc/backup-manager.conf this entry was posted in linux and tagged backup , linux on april 2, 2011 by paulrichards19 . ubuntu sabnzbd+ behind an apache2 proxy this is a guide on how to replace your ugly sabnzbd url to something nice looking thats easier to remember. currently the standard url will run on the port 8080 unless you’ve changed it. you could just change it to port 80 to make a nice url but more likely you already run apache on that port. example old url http://myserver.com:8080/sabnzbd/ new url http://sab.myserver.com assuming you already have apache installed you need to make sure you have the following mod’s installed and enabled. a2enmod proxy a2enmod proxy_http a2enmod proxy_html now you have these installed and enabled you have to created a new vhost entry that will point your chosen server name to your oringal sabnzbd url. servername sab.myserver.com proxypass / http://localhost:8080/ proxypassreverse / http://localhost:8080/ and thats it! reboot your apache server and your done, you can now access via the new url. i would also stronlgly recommend you enable the password protection in your sabnzb configuration. references http://diginc.us/2009/02/ubuntu-sabnzbd-protected-by-an-apache2-proxy-and-htpasswd/ client denied by server configuration error in apache this entry was posted in apache , web tools and tagged apache , sabnzb , ubuntu on october 5, 2010 by paulrichards19 . root your 3uk branded htc desire, 1.22.771.1, add custom recovery this is a quick guide on how to root your 3 (three uk) branded htc desire and add a custom recovery if you wish to load custom roms. before we start here are some details about my phone which i did this process on: htc desire simlock to 3 uk software version 1.22.771.1 hboot 0.80.0000 did this on windows 7 you have 3 choices on what you can do here: put a custom recovery on it to flash any rom you like gain root access your current eclair 2.1 (and a custom recovery if you like) upgrade it to offical froyo 2.2 first we must ‘debrand’ our phone, this is a process where we load a generic rom that shipped with the sim-free desires. these are all version 1.21.x all of which contai

URL analysis for paulsrichards.com

http://www.paulsrichards.com/tag/zend/
http://www.paulsrichards.com/category/jquery/
http://www.paulsrichards.com/tag/backup/
http://www.paulsrichards.com/category/linux/
http://www.paulsrichards.com/tag/android/
http://www.paulsrichards.com/author/steverichards19/
http://www.paulsrichards.com/2008/06/12/nike-data-api-access/#comment-110
http://www.paulsrichards.com/2008/10/01/jquery-plugin-popmenu/
http://www.paulsrichards.com/2011/04/02/how-to-install-backup-manager-on-fedora-and-configure-amazon-s3/
http://www.paulsrichards.com/tag/web-tools/
http://www.paulsrichards.com/category/mysql/
http://www.paulsrichards.com/tag/cars/
http://www.paulsrichards.com/category/apache/
http://www.paulsrichards.com/2008/07/25/improving-table-usabiltity-with-jquery/
http://www.paulsrichards.com/files/downloads/jquery.packed.popmenu.1.0.js
amazon.co.uk
mikesouthby.co.uk

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: PAULSRICHARDS.COM
Registry Domain ID: 90944570_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2015-10-10T22:01:43Z
Creation Date: 2002-10-05T19:15:08Z
Registry Expiry Date: 2017-10-05T19:15:08Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: 480-624-2505
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: NS1.DIGITALOCEAN.COM
Name Server: NS2.DIGITALOCEAN.COM
Name Server: NS3.DIGITALOCEAN.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2017-09-06T02:01:54Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

  REGISTRAR GoDaddy.com, LLC

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =paulsrichards.com

  PORT 43

  TYPE domain

DOMAIN

  NAME paulsrichards.com

  CHANGED 2015-10-10

  CREATED 2002-10-05

STATUS
clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
clientRenewProhibited https://icann.org/epp#clientRenewProhibited
clientTransferProhibited https://icann.org/epp#clientTransferProhibited
clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited

NSERVER

  NS1.DIGITALOCEAN.COM 173.245.58.51

  NS2.DIGITALOCEAN.COM 173.245.59.41

  NS3.DIGITALOCEAN.COM 198.41.222.173

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .