Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Current »

If a user cannot connect to GALRO:

  • Verify that they are using the correct link for production per

  • the first step is to have them clear their browser cache.

Additional notes regarding issues GALRO users have encountered when connecting to GALRO include:

Example 1: DevOps ticket 383367 AEI Login Page is giving 404 error

Production Login: https://secweb.tc.canada.ca/secure/galro-aglie/

Note: the URL is also on pages maintained by the COMMS group. The corresponding links have to be updated and verified on those pages also. For example:


Solution: when login URLs are updated (for example, in the case of gart to secweb, the business the corresponding TC pages, maintained by the communications group have to be updated and verified by the business.
These changes are not handled by development.

Development and Acceptance login pages:

The Login URLs for development and Acc (along with production) are all available on the GALRO External: overview page, currently found in Confluence): GALRO External - AGLIE Externe - BSD - Civil Aviation - Confluence

Example 2: AEI cannot connect to GALRO secweb.

When client connects GALRO does not display correctly - the CLF does not appear to be rendered.
Clicking “English” or “French” directs the user to a blank page.

  • No labels