Support
- Advanced Backup
- Client Side
- Cloud Enterprise
- ColdFusion
- Control Panel
- cPanel
- Customer Portal
- DNS Information
- Dedicated Servers
- DirectAdmin
- Domain Name
- dotDefender
- Dreamweaver
- FileCatalyst
- Front Page
- FTP
- General Information
- Hosted Exchange & SharePoint
- IIS6
- IIS7
- Juniper Netscreen Firewalls
- Linux
- List Server
- MIVA Merchant
- MySQL
- Patching / Server Updates
- phpMyAdmin
- Plesk
- Policies and Procedures
- Premium Spam Filtering
- Programming
- Ruby on Rails
- Search Engine Submission
- SharePoint 3
- SharePoint 2010
- SiteDesigner
- SmarterMail 3
- SmarterMail 4
- SmarterMail 5
- SmarterMail 6
- SmarterMail 7
- SmarterStats
- SmarterTrack
- SQL Server
- Secure Socket Layer (SSL)
- Googlecheckout
- Siteseal
- Ssl
- Enable SSL/TLS for proFTPd in Plesk
- Export SSLs from IIS 6 and IIS 7
- Disable SSL 2.0 in IIS
- Disable SSL 2.0 in Apache
- Check validity of SSL Certificate
- Generate a CSR in IIS
- Generate a CSR on a Linux Server
- Create a PFX File using openssl in Linux
- Generate a Self-signed SSL in Linux
- Install SSL from PFX into IIS
- SSL FAQ
- View SSL Details via Command Line
- Install SSL on cPanel with One IP Address
- Trustwave Site Seal Errors
- Uploading Your Website
- Video Tutorials
- Windows Server 2003
- Windows Server 2008
- Web Design
- WordPress
- Advanced Monitoring
- MediaWiki
- Enkompass
- Microsoft Outlook 2010
- Android
- Outlook Web Access
- Critical Availability Service
- NAS Data Transfer
- Customer Portal Demos
- Joomla
- Moodle
- Cloud Dedicated
- Gallery CMS
- phpBB
- Standard Monitoring
- Righteous Restore
- NAS (Network Attached Storage)
- Networking
- SmarterMail 8
- PCI Security Scan
- LinkTiger
- Windows Cloud VPS
- Linux Cloud VPS
- Linux VPS
- Windows VPS
- Hyper V
- ENSIM
- Alert Logic
- Webmin
- e107
- Vbulletin
- VPN
- Visual Vault
- Mozilla Thunderbird
- PyroCMS
- Active Directory
- Vmware Related
- Drupal
Trustwave Site Seal Errors
This discusses why some users may receive a site seal error after their SSL is installed and how to resolve the issue.
If you are seeing a site seal error such as the below after your Trustwave SSL has been issued and installed, it is likely because Trustwave's database updates every 24 hours. SSL's issued in the same day may not reflect a known identity and thus waiting 24 hours for the site seal to update is common. If the site seal validation does not update after a day, please contact us and we can contact Trustwave on your behalf.
This can also happen when you go to a domain such as https://www.domainname.com but the certificate is actually for the domain https://secure.domainname.com. Further, if the CSR is entered as DoMaIn.com and someone visits https://domain.com, the two don't match due to case sensitivity. In that event, Hosting.com will need to contact Trustwave to have the common name switched to all lowercase.

