Title: Traffic Origin Guard
Author: jasond727
Published: <strong>حوزه‌یران 19, 2026</strong>
Last modified: حوزه‌یران 19, 2026

---

گەڕان لە پێوەکراوەکان

![](https://s.w.org/plugins/geopattern-icon/traffic-origin-guard.svg)

# Traffic Origin Guard

 لەلایەن [jasond727](https://profiles.wordpress.org/jasond727/)

[داگرتن](https://downloads.wordpress.org/plugin/traffic-origin-guard.1.0.0.zip)

 * [وردەکارییەکان](https://ku.wordpress.org/plugins/traffic-origin-guard/#description)
 * [پێداچوونەوەکان](https://ku.wordpress.org/plugins/traffic-origin-guard/#reviews)
 *  [دامەزراندن](https://ku.wordpress.org/plugins/traffic-origin-guard/#installation)
 * [گەشەپێدان](https://ku.wordpress.org/plugins/traffic-origin-guard/#developers)

 [پشتیوانی](https://wordpress.org/support/plugin/traffic-origin-guard/)

## وەسف

Traffic Origin Guard helps protect your origin server from direct traffic by requiring
a secret header value on every request.

Use case:
 – Your site is behind Cloudflare or another reverse proxy. – You want
only proxy-originated requests to reach WordPress. – You want automatic Apache rule
management.

How it works:
 – You set one token in plugin settings. – The plugin writes Apache
rules into .htaccess using a managed block. – Requests missing the expected X-Origin-
Secret header are blocked with HTTP 403.

Features:
 – Apache .htaccess rule writer with managed BEGIN/END markers. – Header
validation status visibility on the settings page. – One-click token utilities in
admin (generate, copy, and “Use as token”). – In-page Cloudflare setup guide with
step-by-step instructions. – Lockout recovery instructions displayed directly in
the settings page. – View details link on the Plugins list page. – Automatic cleanup
on plugin deactivation and uninstall.

## دامەزراندن

 1. Upload the plugin folder to /wp-content/plugins/traffic-origin-guard/.
 2. Activate Traffic Origin Guard from Plugins in WordPress admin.
 3. Go to Settings -> Traffic Origin Guard.
 4. Generate a token using the generator on the settings page.
 5. In Cloudflare, go to Rules -> Transform Rules -> Modify Request Header and add 
    a rule setting X-Origin-Secret to your token on all requests. Do this BEFORE saving
    the token to avoid locking yourself out.
 6. Paste the token into the token field and click Save Token. Confirm the Active server
    rules block appears on the page.
 7. Verify direct origin access without the header returns 403.

## پهد

### Will this lock me out of wp-admin?

Yes, it can if misconfigured. This plugin enforces access at Apache level, so a 
wrong token/header setup can block wp-admin access.

To recover: connect to your server via FTP, SFTP, or your host’s file manager and
open .htaccess in your WordPress root. Find and delete the entire block between (
and including) the lines “# BEGIN Traffic Origin Guard” and “# END Traffic Origin
Guard”. Save the file — your site will be accessible immediately. Then set up your
Cloudflare Transform Rule first before re-entering the token.

### Which servers are supported?

This plugin manages Apache .htaccess rules directly.

### What if .htaccess is not writable?

The plugin cannot enforce protection until .htaccess is writable. Fix permissions/
ownership and save settings again.

### What header name does the plugin check?

X-Origin-Secret

## پێداچوونەوەکان

هیچ پێداچوونەوەیەک نەنووسراوە بۆ ئەم پێوەکراوە.

## بەشداربووان و گەشەپێدەران

“Traffic Origin Guard” نەرمەواڵەیەکی سەرچاوە کراوەیە. ئەم کەسانەی خوارەوە بەشدارییان
تێدا کردووە.

بەشداربووان

 *   [ jasond727 ](https://profiles.wordpress.org/jasond727/)

[“Traffic Origin Guard” وەربگێڕە بۆ زمانەکەی خۆت.](https://translate.wordpress.org/projects/wp-plugins/traffic-origin-guard)

### دەتەوێت بەشداربیت لە گەشەپێدان؟

[گەڕان لە کۆدەکەدا بکە](https://plugins.trac.wordpress.org/browser/traffic-origin-guard/)،
سەیری [تەمارگەی (SVN)](https://plugins.svn.wordpress.org/traffic-origin-guard/) 
بکە، یان بەشداربە لە [ڕووداوتۆماری گەشەپێدان](https://plugins.trac.wordpress.org/log/traffic-origin-guard/)
لە ڕێگەی [(RSS)](https://plugins.trac.wordpress.org/log/traffic-origin-guard/?limit=100&mode=stop_on_copy&format=rss).

## مێتا

 *  وەشان **1.0.0**
 *  دوایین بەڕۆژکردنەوە **2 مانگ لەمەوبەر**
 *  دامەزراندنی چالاک **کەمتر لە 10**
 *  وەشانی وۆردپرێس ** 7.0 یان بەرزتر **
 *  تاقیکراوەتەوە تا **7.0.4**
 *  وەشانی PHP ** 8.3 یان بەرزتر **
 *  زمان
 * [English (US)](https://wordpress.org/plugins/traffic-origin-guard/)
 * تاگەکان
 * [Apache](https://ku.wordpress.org/plugins/tags/apache/)[cloudflare](https://ku.wordpress.org/plugins/tags/cloudflare/)
   [hardening](https://ku.wordpress.org/plugins/tags/hardening/)[headers](https://ku.wordpress.org/plugins/tags/headers/)
   [security](https://ku.wordpress.org/plugins/tags/security/)
 *  [بینینی پێشکەوتوو](https://ku.wordpress.org/plugins/traffic-origin-guard/advanced/)

## هەڵسەنگاندنەکان

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/traffic-origin-guard/reviews/#new-post)

[بینینی هەموو پێداچوونەوەکان](https://wordpress.org/support/plugin/traffic-origin-guard/reviews/)

## بەشداربووان

 *   [ jasond727 ](https://profiles.wordpress.org/jasond727/)

## پشتیوانی

هیچت هەیە بۆ وتن؟ پێویستت بە یارمەتییە؟

 [بینینی مەکۆی پاڵپشتی](https://wordpress.org/support/plugin/traffic-origin-guard/)