- Texada Knowledge Base
- Rental: SRM
- Troubleshooting
-
Top Searched Articles
-
Release Notes
-
Support & Troubleshooting
-
Onboarding Programs
-
SRM Training Videos
-
Sales: Equipment CRM
-
Service: ServiceLink
-
Rental: SRM
-
Handle CRM
-
Rental: Analytics
-
Rental: GateWay
- Getting Started
- New Administration Panel
- Administration Panel
- Administration Panel - CMS
- Administration Panel - Products, Categories, and Attributes
- Administration Panel - Users
- Administration Panel - Requests
- Customer Access Portal
- Customer Access Portal - Rentals
- Customer Access Portal - Invoices
- eCommerce Websites
- eCommerce Websites - Ordering
- Integrations
-
Rental: Texada Mobile
-
Rental: Texada Pay
-
Rental: Texada Web
-
Rental: WorkFlow
-
Sales: Customer Order to Invoice
-
Sales: iMACS
-
Sales: iQuote
-
Service: Condition Monitoring Portal
-
Service: Equipment Monitoring Toolkit
-
Service: Parts & Service Quoter
-
Service: Service Agreement Quoter
-
Sales & Service: CloudLink
-
Sales & Service: Tools
OpenClient Landing Page: "This site can't be reached" Error
How to resolve the “This site can’t be reached” error that appears when attempting to log in to Texada SRM from the OpenClient landing page.
Introduction
Following a recent infrastructure update to Texada SRM, some Texada clients are receiving a "This site can't be reached” error when attempting to access SRM’s login page from the OpenClient landing page (below).
Resolution
This error is caused by the OpenClient landing page redirecting you to the old login URL for Texada SRM. To resolve the issue:
- Navigate to the landing page and hard refresh the screen by pressing ctrl+shift+r (Windows) or ⌘cmd+shift+r (Mac) on your keyboard. The screen will reload and the login buttons should now redirect you to the correct login page.
- If the above solution does not work, try clearing your browser cache. Once your cache has been cleared, the login buttons should redirect you to the correct page.
If you are still experiencing difficulties after attempting both of the solutions above, please contact Texada support.