> Source: [sk122516](https://support.checkpoint.com/results/sk/sk122516)

# sk122516 - "404 page not found" error  when sending translated links to others in Mobile Access

| Property | Value |
|----------|-------|
| Solution ID | sk122516 |
| Date Created | 2018-01-23 |
| Last Modified | 2020-11-12 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |

## Symptoms

- * Should a logged in user send a translated link of a web application he/she is viewing to another logged in user, the latter will receive a "404 page not found" error page from Mobile Access.  
  Same behavior occurs with users who have not logged in yet.
* Mobile Access Blade supports publishing translated URLs for unauthenticated users. Whenever a user clicks such a URL, Mobile Access Blade redirects the client to the login page, and right after authentication, the client is redirected back to the requested URL.  
  The above feature does not work for URLs translated in HT, even when HT URL obfuscation is disabled.

## Cause

In Hostname Translation, the hash at the beginning of the URL is calculated differently per user.

Mobile Access Blade enforces the presence of the CPCVPN_OBSCURE_KEY cookie even when the cookie is not required (i.e., when HT URL obfuscation is disabled). Since unauthenticated users don't yet present that cookie, they are rejected with a 404 error response.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content