Frequently Asked Questions

1. Take your main server images or any important files backup.
2. Log in to the admin ID:
   • Go to the Backup section
   • Click the Generate Backup Now button
   • Download latest backup file from: /home/xtreamaster/backups/
3. Server Migration:
   • Login to Master CMS cPanel (ID: xm:********)
   • Delete existing server
   • Please input the new server or re-install the server OS, then insert the SSH details.
   • Wait for installation completion
4. Backup Restoration:
   • Upload *****.sql.gz to /home/xtreamaster/backups/
   • Login with admin/admin credentials
   • Navigate to Backup section
   • Click Restore Backup button
5. Update Main Server IP: (Optional if main server changed)
   • Login to Xtream-Masters CMS cPanel (ID: xm:********)
   • The system will automatically update the main server IP in the database if it changes.
6. Troubleshooting Load Balancers:
   • Navigate to Manage Server section
   • For each load balancer:
     Click option button
     Select Restart Service
   • Wait up to 2 minutes for load balancer become online.

Port Change

To change panel default port 7709

• Login to Xtream-Masters CMS cPanel (ID: xm:********)
• In dashboard Click Edit Port Button
• Set New port Make sure not already used by any other service Then click Save button
• Approximately 2 minutes will take to apply changes and You all Done.

1. Access Code Configuration:
   • Log in to your admin panel
   • Navigate to System Security > Access Code
   • Enable both options:
     • "Enable access code feature for panel logins"
     • "Disable panel login page without access code link"
2. Create Admin Panel Code:
   • Click Create New Code (top of page)
   • Generate code using generate icon
   • Configure settings:
     • Type: Admin Panel
     • Select admin groups
     • Optional: IP restrictions
   • Click Add
3. Reseller Panel Setup:
   • Repeat admin process for reseller panel
   • Best Practice:
     • Create multiple codes for different reseller types
     • Helps identify attack sources through targeted codes
4. Secure Mags Portal:
   • Create Mac Access code:
     • "Enable access code mags portal instead use default /c"
     • Helps identify attack sources through targeted codes or if you don't use mac never share code with any
5. Final Implementation:
   • Copy generated access code links
   • Distribute to authorized users:
     yourdomain.tld:port/ac_XXXXXXX

1. Backup MySQL Data
   • Create complete database backups
   • Download backup files to your local PC
   • Do not proceed without verified backups
2. Remove Existing MySQL Server
   # Execute these commands in sequence:

   sudo service mysql stop
sudo apt-get --force-yes remove mysql-server mysql-client
sudo apt-get --force-yes purge mysql-server mysql-client
sudo apt-get --force-yes remove mysql-common -y
sudo apt-get --force-yes purge mysql-common -y
sudo apt-get --force-yes autoremove --purge -y
sudo apt-get autoclean
sudo rm -rf /etc/mysql
sudo rm -rf /var/lib/mysql
sudo rm -rf /var/log/mysql
   

   Copy all commands carefully
   This will completely remove MySQL and all associated data. Ensure backups exist before proceeding.
3. Install Panel
   • Enter server SSH details in Master CMS panel
   • Initiate installation process
   • Verify installation finish

Some users are configuring their systems improperly, often without understanding how they work, which leads to system issues. They then contact support, reporting problems such as system failures or poor streaming performance.
To help you achieve optimal streaming results, please follow the detailed configuration guidelines provided below.

• Disallow 2nd IP Connection Instead Use Video Logs Feature.
• Restart on Audio Loss (Can break uptime) Instead use Stream Analyzer

1. Method 1
   • Login to Master CMS cPanel (ID: xm:********)
   • Edit Main server
   • Set New IP And Click Save
2. Method 2
   • Login to Master CMS cPanel (ID: xm:********)
   • Download Config Backup
   • Update IP And Restore Config.
3. Update Main Server IP In DNS.
4. Troubleshooting Load Balancers:
   • Navigate to Manage Server section
   • For each load balancer:
     Click option button
     Select Restart Service
   • Wait up to 2 minutes for load balancer become online.

1. Identify the Issue:
   • Playlist loads = Panel connection is working
   • Streams won't play = DNS misconfiguration or MAG Security disabled
   • MAC uses playlist DNS for streaming, not panel DNS
2. Check Main Server DNS Configuration:
   • Navigate to Servers Page → Edit Main Server
   • Carefully review ALL three DNS input fields:
     • Users CDN: Must point to main server IP
     • Private Users CDN: Must point to main server IP
     • Proxy IP or DNS [All]: Must point to main server IP
3. Enable MAG Security:
   • Go to General Settings
   • Navigate to Stalker Portal Tab
   • Enable MAG Security option
   • Save the settings
   Note: MAG Security must be enabled for MAC devices to authenticate and stream properly.
4. Common DNS Mistakes to Fix:
   ❌ Wrong Configurations

   • Spelling errors: yourdns.xy instead of yourdns.xyz
   • Wrong server pointed: DNS pointing to load balancer instead of main server
   • Missing DNS record: Domain added but A record not created
5. Apply Correct Configuration:
   • Ensure at least one DNS field contains valid domain
   • Verify domain's A record points to main server IP
   • Confirm MAG Security is enabled
   • Save changes in server settings
   • Wait 2-3 minutes for propagation
   • Test MAC device again

1. Admin Controls - Set Category Order in Bouquets:
   • Navigate to Bouquets Management
   • Edit any bouquet
   • Join and sort categories to reorder them
   • Example arrangements:

     European Bouquet:

     • 1. UK Channels
     • 2. German Channels
     • 3. French Channels
     • 4. Other regions...

     Arab Region Bouquet:

     • 1. Arabic Entertainment
     • 2. Arabic Sports
     • 3. Arabic News
     • 4. International...


2. Reseller Controls - Reorder Bouquets:
   • Reseller can also sort Bouquets as thier clients Requirements
   • Go to Edit Line for any user
   • In bouquet selection area, use arrows to move bouquets up/down
   • Most relevant bouquet appears first for their customers
   • Save changes to apply new order


3. Practical Use Cases:
   💡 Smart Organization Examples

   • For UK Reseller:
     • Place UK Sports at top during Premier League season
     • UK Entertainment channels follow
     • International content at bottom
   
   
   • For Arabic Reseller:
     • Ramadan channels first during holy month
     • Arabic series and movies next
     • Kids Arabic content for family packages
   
   
   • For Sports Package:
     • Live sports channels at top
     • Sports news channels second
     • General entertainment last
4. Setting Up Regional Bouquets:
   • Create separate bouquets for each region
   • Assign appropriate resellers to regional bouquets
   • Let resellers fine-tune order for their market
   • Monitor user engagement to optimize further

1. Create a user line with:
   • Minimum 10 connections
   • All channel bouquets should be subscribed
2. Configure Player Credentials:
   • Go to General Settings > Xtream tab
   • Input the created line username/password in Player Credentials section
   • Click Save
3. Access Stream Configuration:
   • Navigate to Mass Tools > Streams Tools
4. Enable Stream Analysis:
   • Switch to Stream Analyzer tab
   • Enable Auto stream analyzer
5. Final Configuration:
   • Configure your server Streaming DNS
   • Adjust other settings as needed
   • Click Save
6. Monitoring
   • Goto Streams Page
   • Check Status column
   • If first icon red means on_demand source down or slow
   • If secound icon red means source down more then 7 days and remove from user list until fix

1. Enable VideoLog System:
   • Navigate to General Settings > Streaming Tab
   • Enable Connections Exceed VideoLog option
   • Save changes
2. Advanced Connection Monitoring:
   • System will now show to Client the video message log instead of playback error:
     "Your connection limit reached!
     Active sessions: [X/X connections]
     Devices and new attempt details
     Stop streaming on other devices or change line password"
   • Real-time connection tracking displays:
     • Allowed concurrent connections
     • Currently used connections
     • Attempt history of excess usage

1. Login SSH
   • Go to: `/home/x_m/bin/nginx/logs/` to clear log files.
   • Use command: df -h to check the overall disk usage and status.
   • Use command: du -sh /home/* to check the size of each folder in the home directory.
   • Identify which folder is using the most disk space.
   • If you need more detail, navigate into the large folders with: du -sh /home/your-folder/* to list individual file sizes.

1. Check Overall Disk Usage
   • Run df -h to see disk usage across all mounted filesystems
   • Look for /home or root (/) filesystems with high %Use
2. Identify Large Directories
   • Check /home directory size: du -sh /home
   • List directories sorted by size:
     du -sh /home/* | sort -rh
   • Drill down into large directories:
     cd /path/to/large-dir && du -sh * | sort -rh
3. Find Large Files
   • Find files larger than 1GB:
     find /home -type f -size +1G -exec ls -lh {} \;
   • Sort files by size in current directory:
     ls -lahS
4. Common Cleanup Targets
   • Clear old log files: /var/log and application log directories
   • Check for core dumps: find / -name core -size +100M
   • Clean package cache: apt-get clean or yum clean all

If you getting Mysql database connection failed message while to login panel, you can follow these setups.

1 - Log in to your main server using the 'PuTTY' program and run this command.

sudo service mysql restart

1. 🔑 Admin Recovery: Log in to your master cms Cpanel id that starts from xm:

   → Click Reset admin access in narbar menu
   → Change the admin id password

1. 🔑 Admin: Log in to your admin panel id.

   → Menu Manage server page then edit the spacific server
   → Goto Advance tab
   → Select Correct Network interface and save it
   → Optional: Find correct Network interface run cmd into following server ifconfig
2. If bandwidth start showing but users & connections statistics not showing follow this FAQ: 0 Connection On LB

1. 🔧 Server Setup:

   Login your main server putty and run the provided cmd below.

   wget -O "/home/xtreamaster/wwwdir/adminer_579632.php" https://github.com/vrana/adminer/releases/download/v5.4.1/adminer-5.4.1-en.php
2. 🌐 Access Adminer:

   Now access adminer by this link →

   http://{your_streaming_dns}:{streaming_port}/adminer_579632.php?server=127.0.0.1:7999
3. 🔑 Database Access:

   Now login into your Master CMS cPanel with ID that start from XM: Then edit your main server a modal will open where you can find your database login info.

1. ⚙️ Configuration Update:

   Goto settings page and click Update Tables button.

2. 🚀 Now Bring Servers Online.

   Main Server

   1. Goto Servers Page, Edit Main Server Set SSH Password
   2. Navigate to: Servers Page → Click Main Option → Restart Service

   Load Balancers

   1. Edit Down LB Set SSH Password (if not set already)
   2. Navigate to: Servers Page → Click LB Option → Restart Service (OR) Re-install Balancer

1. Start Restoration & Immediately Disable Web Access:
   • Click Restore Database in your admin panel
   • Immediately after clicking restore, open SSH and run:
     root@server:~#

     mv /home/xtreamaster/wwwdir /home/xtreamaster/wwwdir.disabled
   • This instantly blocks all incoming requests, modifications, and log inserts
   • System can now focus 100% on restoration without interruptions
2. Monitor Restoration Progress:
   • Your admin panel will become inaccessible during restoration
   • Periodically try to access any dashboard page
   • Restoration is complete when: You can successfully load any admin panel page again
   Testing tip: Keep refreshing your browser on the dashboard page. When it loads instead of showing an error, restoration is complete.
3. Re-enable Web Access After Completion:
   • Once you confirm restoration is complete (panel accessible), run:
     root@server:~#

     mv /home/xtreamaster/wwwdir.disabled /home/xtreamaster/wwwdir
   • Web access is now restored and system operates normally

1. Fix DNS Configuration:
   • Navigate to Servers Page → Edit Main Server
   • Locate the three DNS input fields and read each info icon carefully
   • Critical: Set your DNS in Proxy IP or DNS [All] field
     Example: streaming.yourdomain.com
   • This DNS must point to your main server IP
   • Save the configuration


2. Understanding DNS Fields Priority:
   • Users CDN: For normal users (optional)
   • Private Users CDN: For users with Private CDN enabled (optional)
   • Proxy IP or DNS [All]: Default fallback - REQUIRED
   If Users CDN is not set, all connections will use the Proxy IP or DNS [All] field. This field is mandatory for proper DNS operation.


3. Fix Existing Channel Icons:
   • If your main server ip coming in channels icon
   • menu Channels Advanced Streams Tools > Logo DNS Changer
   • Add YOUR_OLD_IP which comes out in playlist.
   • Replace your.dns.com with your configured DNS


4. Verify Changes:
   • Wait 10 minutes to update playlist cache.
   • Generate a new playlist for testing
   • Check that URLs now show DNS instead of IP
   • Verify channel icons use DNS in their paths

1. 🔑 Port Setup:

   1. Login to your Xtream-Masters CMS panel (Master-ID starting with xm:)
   2. Set SSL-supported port for admin panel from these options:
      2053, 2083, 2087, 2096, 8443

   ⚠️ Important: Ensure selected port isn't used by other services (e.g., streaming ports)

2. 🔌 SSL Activation:

   Method 1

   ☁️ Cloudflare Automatic SSL

   1. Add your domain to Cloudflare
   2. Point your server IP as `A` DNS record with Cloudflare proxy enabled
   3. Goto SSL Section Set SSL -> Off
   4. SSL will activate automatically within 5 minutes

If you have VODs not working after migration that's normal becouse of core change you need re-encode agian, for that we've created an automated one-click tool that you can use.

If your main server Request per sec: 500 or Load-Balancer Request per sec: 200 above, your server is under ddos attack, follow below the steps to protect your server.

1. Menu → Manage server page
   • Edit main / LBs server
   • Goto Server Guard tab
   • Enable Server Guard
   • Enable i'm under attack mood
   • Enable botnet fighter
   • Read the all avaliable option with full attention and do config then save it.
2. Admin Profile → Goto General Settings Page
   • Click Xtream Tab
   • Disable XML EPG - ON
   • Disable Player_API EPG - ON
   • And Save Config.
3. Admin Profile → Goto General Settings Page (Additional)
   • Click BruteForce Attacks Tab
   • Enable All Checkbox
   • Requests Amount for Blacklist 25
   • In Seconds 5
   • Requests Within Seconds 10
   • Flood Limit 30
   • And Save Config.

Note: monitor blocked ip page if you found any restreamer ip blocking as well adjust the config accordingly

1. Smart Password Management:
   • Use unique passwords for each server - never reuse
   • Minimum 16 characters with mixed case, numbers, symbols
   • Never save real passwords in plain text files
   • Avoid sharing passwords via WhatsApp, Telegram, email
   💡 Pro Tip: Password Obfuscation

   Store passwords with a personal pattern only you know:

   Real Password: Example@123#Server
Stored as: Example%123$Server
Your Pattern: Replace % with @ and $ with #

   Create your own unique substitution pattern that only you understand.

2. Enable Server Guard (IP Whitelisting):
   • Navigate to Manage Servers → Edit Server
   • Go to Server Guard tab
   • Enable SSH IP Whitelist
   • Add your office/fixed vpn IP addresses
   • Enable Block all other IPs
   Even if your password is compromised, attackers can't access SSH without being on the whitelist.
3. Regular Security Practices:
   • Monthly password rotation for critical servers
   • Monitor SSH logs for failed login attempts:
     tail -f /var/log/auth.log
4. Panel-Specific Security:
   • Use Access Codes for admin panel login
   • Regularly check Admin Activity Logs

If you want to change the VOD server by transferring files to the new load balancer, follow these three easy steps. (Make a database backup so any mistakes can be easily undone.)

1. Menu → Mass Tools → Streams Tools
   • DNS Replacement Tab
   • OLD String example → s:123:/home/your_folder
   • New String example → s:150:/home/your_folder
   • This Will replace server ids in movies, episodes path.
2. Menu → Movies / Epsiodes → Mass Edit
   • Select Moved Content
   • Select New Server And Save it.
3. Menu → Mass Tools → Advanced Tools
   • Proceed Mass Encoding.

1. If you install a new load balancer server and you see that even if clients are inside, connections are zero, you need to enter follow cmd in your main server SSH:
   root@server:~#

   sudo -u xtreamaster /home/x_m/bin/php/bin/php /home/xtreamaster/tools/connection_handler.php >/dev/null 2>/dev/null &

If you are experiencing the same issue, please run the following query to resolve it:

UPDATE series_episodes AS se SET se.sort = se.episode_num;

take database backup first.

1. In general settings menu–> 𝙨𝙚𝙘𝙪𝙧𝙞𝙩𝙮 turn OFF or NO these options:
   • Override Client's Country upon first connection
   • Verify Client-IP During Load Balancing
   • Disallow connections with empty user agent
   • Don't allow connections from Different IPs while User is online
   • Enable ISP Lock Mode
   • Disallow Following Proxy Types Connections UN-SELECT THEM ALL
   • Allow connections from these countries transfer all countries on the right side
2. In general settings menu–> Anti-Abuse/BruteForce Attacks turn everything to “NO”. Delete all blocked IPs from 𝙨𝙚𝙘𝙪𝙧𝙞𝙩𝙮 plug-ins. Delete all blocked subscriptions from logs–> Abused Subscriptions
3. In general settings menu–> Performance Turn everything to “NO” except the Save Error Client Log so you can check any error log from client req. logs menu.
4. In general settings menu–> Stalker Portal
   • UN-select all the images in that menu. Please DO NOT select any image from the Lock STB To Images otherwise you will block the other clients!
   • Check your “allowed stb types” and transfer everything to the right side.
   • Increase MAG 𝙨𝙚𝙘𝙪𝙧𝙞𝙩𝙮 set this to “NO”
5. In general settings menu–> Streams Put the default values as suggested in “i” icon.
6. In general settings–> steraming and client settings
   • Balance Connections by set this to Number of connections
   • Prebuffer enable for Restreamers Set this To “NO”
   • Use Buffer to store the Data Before Sending them to client Set to “NO”
7. In TOOLS run:
   • Reset Country restriction for all subscriptions
   • Remove Network Logs (RUN THIS OFTEN)
   • Remove MAG Lock
   • Reset all ISPs
   • Delete closed connections
8. In manage servers menu, check the servers max allowed connections. Do NOT have them in 0!
9. Please note that you MUST clear your panel logs very often

1. Understanding Stream Priority Behavior:
   • By default, the system prioritizes the first backup stream if it's online
   • This prevents automatic switching to other backup sources
   • The setting controls whether to stick with the first working source or cycle through all backups
2. Configure Backup Stream Switching:
   • Navigate to General Settings → Streaming tab
   • Locate Priority First Backup Stream option
   • Configure based on your needs:
     • Enabled: System uses first available backup and stays with it
     • Disabled: System cycles through all backup sources sequentially when failures occur
   • Click Save to apply changes
3. Recommended Configuration:
   • For Stability: Keep enabled if your first backup is reliable
     Use Case

     Best when you have a high-quality primary backup that rarely fails

   • For Redundancy: Disable to utilize all backup sources
     Use Case

     Best when you have multiple backup sources and want maximum failover protection

4. Verify Source Switching:
   • Test with a channel that has multiple sources configured
   • Temporarily disable the primary source to trigger failover
   • Monitor if system switches to next available source
   • Check stream logs to confirm switching behavior

1. DNS Configuration:
   • Go to Servers Page > Edit Load-Balancer Server
   • Read all information in the three DNS input fields carefully (Then come back to this article)
   • Use Domain DNS under CDN (cloudflare or any other)
2. Domain Strategy:
   • Basic Requirements:
     • Use Cloudflare's free or paid plan by add multiple domains in Cloudflare and create mutiple sub-domain of each domain
     • Domain names MUST NOT contain: ott, stream, iptv
     • Use random names like bluewidgets24[.]tld
3. DNS Configuration:
   • Navigate to Servers Page > Edit Load-Balancer Server
   • Configure users DNS fields with these strategies:
     1. Field 1 - Users CDN: Set Cloudflare Free Plan DNS
     2. Field 2 - Private Users CDN: Set Cloudflare Premium Plan DNS
   • Somecase If ISPs blocking free plan IPs We enable Private CDN Option in trusted Users Lines that will connect with Field 2 - Private Users CDN
4. URL Pattern Obfuscation:
   • However, if your ISP is still smart enough to block URLs based on their format (for example, a format like {string}/{string}/{int}.ts) you can also rewrite the URLs:
     • Go to General Settings > Streaming
     • Enable Secure LB Connection
     • This Will Rewrite URLs automatically and make more hard to deduct IPTV Stream links for ISP

1. Remove cron file restrictions:
   • Execute command: sudo chattr -i /var/spool/cron/crontabs/root
2. Edit root cron jobs:
   • Open crontab editor: crontab -e
   • Add these entries:

     0 5 */7 * * /sbin/reboot
     @reboot bash /home/xtreamaster/services_checker.sh

   • Save and exit the editor
3. Lock cron file:
   • Apply immutable attribute: sudo chattr +i /var/spool/cron/crontabs/root

1. Edit Real IP Configuration File:
   • Access your main server via SSH
   • Open the configuration file:
     root@server:~#

     nano /home/x_m/bin/nginx/conf/realip_cloudflare.conf
2. Add Your Proxy IP:
   • Add this line at the TOP of the file:
     set_real_ip_from YOUR_PROXY_IP/32;
   • Example with actual IP:
     set_real_ip_from 91.92.91.92/32;
   • For multiple proxies, add each on a new line:
     set_real_ip_from 91.92.91.92/32; set_real_ip_from 185.123.45.67/32;
   • Save file: Press Ctrl+X, then Y, then Enter
3. Test Configuration:
   • Verify nginx configuration is valid:
     root@server:~#

     /home/x_m/bin/nginx/sbin/nginx -t
   • You should see:
     nginx: configuration file test is successful
4. Apply Changes:
   • If test passed, reload nginx:
     root@server:~#

     /home/x_m/bin/nginx/sbin/nginx -s reload
5. Verify Real IP Detection:
   • Check admin panel → Online Users
   • Client real IPs should now appear instead of proxy IP
   • Geolocation and ISP detection should work correctly

1. Create Telegram Bot:
   • Open @BotFather in Telegram
   • Send /start command
   • Send /newbot to create new bot
   • Follow naming instructions:
     BotFather:

     Choose a name for your bot (e.g., MonitoringBot) Now choose a username for your bot. It must end in 'bot' (e.g., MyMonitoringBot)
2. Copy Bot Token:
   • After successful creation, copy the API token
     Security Alert: This token is like a password. Never share it!
   • Visit your bot link: t.me/YourBotUsername
3. Add Bot to Channel/Group:
   • Go to your bot profile → "Add to group or channel"
   • Select your target channel/group
   • Make bot admin with posting permissions
4. Find Chat ID:

   For Channels:

   • Your Chat ID is the channel username
   • Format: @yourchannelname
   • Example: For t.me/mychannel → Chat ID: @mychannel

   For Groups:

   1. Add @chatid_echo_bot to your group
   2. Send any message in the group
   3. The bot will reply with your Group Chat ID (numeric format)
   4. Format: -1001234567890

1. Access Server Configuration:
   • Login to your main server via SSH
   • Navigate to nginx configuration directory:
     root@server:~#

     cd /home/x_m/bin/nginx/conf/
   • Edit the main configuration file:
     root@server:~#

     nano nginx.conf
2. Add Real IP Configuration:
   • Find the http { block in the configuration
   • Add these lines inside the http block:
     set_real_ip_from 0.0.0.0/0;
real_ip_header X-Forwarded-For;
real_ip_recursive on;
   • Save file: Press Ctrl+X, then Y, then Enter
3. Apply Configuration:
   • Test nginx configuration:
     root@server:~#

     /home/x_m/bin/nginx/sbin/nginx -t
   • If test passes, reload nginx:
     root@server:~#

     /home/x_m/bin/nginx/sbin/nginx -s reload
4. Verify Real IP Detection:
   • Check user connections in admin panel
   • Real client IPs should now appear instead of proxy IPs
   • Check logs to confirm proper IP logging:
     tail -f /home/x_m/bin/nginx/logs/access.log

1. Identify the Issue:
   • User reports device not working despite active subscription
   • Other devices on same portal link work fine
   • Usually affects MAG boxes or devices with aggressive connection retry
   • System auto-blocks MAC after detecting excessive hits
2. Unblock Specific MAC Address:
   • Login to main server SSH
   • Run command with the blocked MAC address:
     root@server:~#

     rm -rf /home/xtreamaster/tmp/MAC_ADDRESS_hits
   • Example for MAC 11:22:33:44:55:66:
     root@server:~#

     rm -rf /home/xtreamaster/tmp/11:22:33:44:55:66_hits
3. Flush All Blocked MACs (Optional):
   • To unblock all MAC addresses at once:
     root@server:~#

     rm -rf /home/xtreamaster/tmp/*_hits
   • Use with caution: This removes all MAC blocks system-wide
4. Verify Unblock:
   • Ask user to restart their device
   • Device should connect immediately after unblock
   • No service restart required

1. Install Squid:
   root@server:~#

   apt update && apt install squid -y
2. Backup & Replace Configuration:
   root@server:~#

   
   cp /etc/squid/squid.conf /etc/squid/squid.conf.backup
rm /etc/squid/squid.conf
nano /etc/squid/squid.conf
3. Paste This Ready Configuration:
   # Simple Squid Proxy Configuration
http_port 4444
acl all src 0.0.0.0/0
http_access allow all
tcp_outgoing_address 0.0.0.0 all
dns_nameservers 8.8.8.8
dns_v4_first on
   • Save: Press Ctrl+X, then Y, then Enter
4. Restart Squid:
   root@server:~#

   systemctl restart squid
systemctl enable squid
5. Proxy is ready:
   • SERVER_IP:4444
   • Example: 123.123.123.123:4444