is that in the web setup gui? I've seen this where in Firefox you have to manually import the CA cert before the admin cert will load. Cheers, Brian

Ok, I have started again. Deleted all certs from Firefox and Windows Certificates MMC. Executed the following and I still get no further from the Admin user screen. Can anybody shed some light please? Set hostname FQDN enable remi and remiphp55 yum -y install perl php httpd Edit /etc/hosts - add system name and ipaddress setenforce 0 chkconfig iptables off service iptables stop yum -y install wget wget http://mirror.bytemark.co.uk/fedora/epel/6/x86_64/epel-release-6-8.noarch... http://remi.check-update.co.uk/enterprise/remi-release-6.rpm yum localinstall *.rpm -y useradd ds389 yum -y install 389-ds /usr/sbin/setup-ds.pl yes yes 2 dogtag.domain.com apache apache 389 dogtag dc=domian, dc=com cn=Directory Manager service httpd start service dirsrv start chkconfig dirsrv on chkconfig httpd on yum -y install pki-ca wget http://b72e18005286881a03f27d32.fcc.netdna-cdn.com/wp-content/uploads/201... mv dogtag_fedora_theme.tar.gz?7e26d5 dogtag_fedora_theme.tar.gz rpm -e ipa-pki-common-theme-9.0.3-7.el6.noarch ipa-pki-ca-theme-9.0.3-7.el6.noarch --nodeps tar -zxf dogtag_fedora_theme.tar.gz yum -y localinstall dogtag-pki-kra-theme-9.0.15-1.fc17.noarch.rpm dogtag-pki-tps-theme-9.0.15-1.fc17.noarch.rpm dogtag-pki-ocsp-theme-9.0.15-1.fc17.noarch.rpm dogtag-pki-ra-theme-9.0.15-1.fc17.noarch.rpm dogtag-pki-common-theme-9.0.15-1.fc17.noarch.rpm dogtag-pki-theme-9.0.15-1.fc17.src.rpm dogtag-pki-console-theme-9.0.15-1.fc17.noarch.rpm dogtag-pki-tks-theme-9.0.15-1.fc17.noarch.rpm yum -y localinstall dogtag-pki-ca-theme-9.0.15-1.fc17.noarch.rpm pkicreate -pki_instance_root=/var/lib -pki_instance_name=domain-ca -subsystem_type=ca -agent_secure_port=9443 -ee_secure_port=9444 -ee_secure_client_auth_port=9446 -admin_secure_port=9447 -unsecure_port=9180 -tomcat_server_port=9701 -user=pkiuser -group=pkiuser -redirect conf=/etc/domain-ca -redirect logs=/var/log/domain-ca -verbose service httpd restart service dirsrv restart Browse to supplied URL at end of previous command Next Next New CA CA Name = Domain Domain CA Next New CA Subsystem Subsystem name = Domain Ltd Certificate Authority Next Make this a Self-Signed Root CA within this new PKI hierarchy. Next Enter Directory Server password Next Use the default key size (2048 bits). Next Prepend all nicknames with TPG DogTag Next Apply Next Export subsystem keys and certificates Password Next Save File then do the following: Rename savepkcs12 to savepkcs12.p12 Start --> Run --> mmc --> Enter File --> Add/Remove Snapins --> Computer Account --> Local Computer --> Ok --> Ok Open Trusted Root Certification Authorities Open Certificates Right Click Certificates --> All Tasks --> Import Next Browse to File Next Password Next Next Finish Ok Back to Browser click Next Import same file into Browser Next Enter Admin UID Name Email Password Next On 19/01/2015 22:34, Kobus Bensch wrote: -- Trustpay Global Limited is an authorised Electronic Money Institution regulated by the Financial Conduct Authority registration number 900043. Company No 07427913 Registered in England and Wales with registered address 130 Wood Street, London, EC2V 6DL, United Kingdom. For further details please visit our website at www.trustpayglobal.com. The information in this email and any attachments are confidential and remain the property of Trustpay Global Ltd unless agreed by contract. It is intended solely for the person to whom or the entity to which it is addressed. If you are not the intended recipient you may not use, disclose, copy, distribute, print or rely on the content of this email or its attachments. If this email has been received by you in error please advise the sender and delete the email from your system. Trustpay Global Ltd does not accept any liability for any personal view expressed in this message.