Nulled For ALL Modules Garden

l1admin689
Admin
Moderating
Bronze Member
Iron Member
Joined
May 31, 2020
Messages
1,854
Reaction score
1,341
Credits
$2,442
you need to change hosts file to null it with default method.so All hosting can not support this method .
Null patch was work For ALL VPS .
Patch was not work with new version.because some was use Cert vaild to send data.
1.change hosts with our active server ip


Important:
Someone want to test for active success or fail .you can run this php file to check.


2. login whmcs.nullpro.ru to register and free get license code
3.change license.php with our license key .
2024-09-13_074803.webp

if you want to change domain or install folder ,you need to click reissue button to reset it and then enjoy

4.enjoy it.

How to edit hosts file in Windows?​

  1. Press Start and find Notepad. Right-click to Run as administrator.
windows-notepad.webp
  1. Once in Notepad, go to File Open. Get to C:\Windows\System32\Drivers\etc and make sure to select All Files to find the hosts file.open-hosts-file-1024x572.webp
  2. Now you can edit the hosts file. Add the custom IP address you’ve made earlier, followed by a space, then your domain nameadd-ip-address-on-hosts-file-1024x587.webp
  3. When you’re finished, don’t forget to save your changes.

How to edit hosts file in Linux?​

In Linux, you can use your favorite text editor to do the job. Here, we will use Gedit in Ubuntu. Open the Terminal by pressing Ctrl+Alt+T.

  1. Type the command below, then key in your admin password:
    sudo su
    ubuntu-terminal.webp
  2. To open the hosts file using Gedit, type the following command and press Enter:
    sudo gedit /etc/hosts
    ubuntu-gedit-hosts-file.webp
  3. Add the targeted IP address followed by a space, then the domain name at the bottom of the hosts file, just like on the Windows 10 tutorial.

How to Locate and Edit the Hosts File on macOS?​

Let’s start by finding and opening the hosts file.

1. Open the Hosts File

Follow these steps to access your hosts file on a Mac:

2. Open Terminal by searching it via the spotlight search (Command + Spacebar keys).

Finder-window-displaying-search-results-for-terminal-1024x192.webp
3. Open the hosts file with your preferred editor program. In this tutorial, we will use the Nano text editor. To open it, enter the following:

sudo nano /private/etc/hosts
4. Since we use sudo to edit the hosts file, you will be asked to enter the administrator password of your macOS user account. Type your admin password and hit the Enter key.
The-terminal-window-displays-the-original-hosts-file-that-is-opened-with-the-nano-text-editor...webp

Important! For security reasons, the cursor doesn’t work in the command line. Use the arrow keys to navigate between the lines inside the hosts file.
5. Edit the Hosts File on a Mac

To emulate DNS settings and point a domain name to an IP address, use the following syntax:

IP_Address domain.com
IP_Address www.domain.com
For example, to emulate the DNS change for whmcs.nullpro.ru and www.nullpro.ru, you would have to include the following lines at the bottom of the hosts file.

185.185.185.185 www.nullpro.ru
185.185.185.185 nullpro.ru
185.185.185.185 whmcs.nullpro.ru
This will emulate the IP address change of the nullpro.ru domain and www.nullpro.ru subdomain to 185.185.185.185.
2024-08-12_021202.webp
Once you are done editing the hosts file, press Control + X on your keyboard. Enter Y to save the changes, and hit the Enter button.

Now, your Mac will resolve the hostinger.com domain using the given IP address instead of what is set at the DNS Zone.

Editing the hosts file can also help you see your new site content during the propagation period after connecting a domain to web hosting. Remember that after propagation is done, you should remove the new lines from the hosts file.

6. Flush DNS Cache

The hosts file changes may not apply instantly. You can flush the DNS cache to help speed up the process. To flush a Mac’s DNS cache, execute the following command:

macOS Monterey, Big Sur
Bash:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
macOS Catalina, Mojave, High Sierra, Sierra, Mountain Lion, Lion
Bash:
 sudo killall -HUP mDNSResponder
 
Last edited:
hi,Follow the steps to appear
Connection cannot be established. Please report your server's IP address to support@modulesgarden.com (No Connection)
How to solve it

i can not find event that you have use this key "896d161a86" to connect this actived server . and it was reissued status .
yours:
2024-09-11_215314.webp
right:
2024-09-11_215212.webp

your need to check All Step
 
Last edited:
i can not find event that you have use this key "896d161a86" to connect this actived server . and it was reissued status .
yours:
View attachment 85355
right:
View attachment 85354

your need to check All Step
Create a license.php file under proxmoxvps and write <?php
/*
* LICENSE:
* Please provide your Proxmox VPS Module For WHMCS license below
*/
$proxmox_vps_licensekey="ModulesGarden_ProxmoxVPS_896d161a86";
etc/hosts/

Still can't connect
 
Last edited by a moderator:
Create a license.php file under proxmoxvps and write <?php
/*
* LICENSE:
* Please provide your Proxmox VPS Module For WHMCS license below
*/
$proxmox_vps_licensekey="ModulesGarden_ProxmoxVPS_896d161a86";
etc/hosts/

Still can't connect
do you view ping www.modulesgarden.com result ? is it right or require to clear cache?
 
Last edited:
do you view ping www.modulesgarden.com result ? is it right or require to clear cache?
ping www.modulesgarden.com
PING www.modulesgarden.com (right IP) 56(84) bytes of data.
Unable to ping
curl -I www.modulesgarden.com
HTTP/1.1 302 Found
Server: nginx
Date: Thu, 12 Sep 2024 13:34:31 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Set-Cookie: WHMCSmgVBhRu6mOSd=qs8oqufs5vfib7e420htjov148; path=/; secure; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Location: https://whmcs.nullpro.ru/index.php
Strict-Transport-Security: max-age=31536000
Alt-Svc: quic=":443"; h3=":443"; h3-29=":443"; h3-27=":443";h3-25=":443"; h3-T050=":443"; h3-Q050=":443";h3-Q049=":443";h3-Q048=":443"; h3-Q046=":443"; h3-Q043=":443"
 
Last edited by a moderator:
Pinging this domain name does not return
The domain name resolution is successful to right ip
 
Last edited by a moderator:
Top