# Best Practices & Common Issues
## Best Practices 💯
When running bots on datacenter servers or home servers, there are some tips and tricks you should be aware of to ensure utmost uptime and performance.
* Maintain Windows always up to date, in some cases it can even cause random system restarts if not kept up to date.
* Make 2 disk partitions, keep the main VM in one of them and the clones in the other one.
* Use 0.8 - 1 values on account's limit resources.
* Always keep your VMWare window closed, having the VMs opened displaying the bot working consumes a lot of CPU and GPU, only open them when necessary (checking out a problem).
* Set a a 60-120 seconds delay on GydrusManager's "start\_vm\_delay" feature. This will spread out the CPU usage to not cause 100% usage spikes, which could lead to issues.
* Use the recommended exact VMWare version shown in [Download necessary files](/first-steps/download-necessary-files.md#vmware-workstation-15).
* Keep your drivers up to date, if you are using datacenter servers you can ask the staff for specific links for different server models.
## Common Issues :warning:
Some issues that could show up when running your bots and their solutions.
### VM Clone numbers as "-"
On Server's tab in each server item, you have each account's VM clone number.
Due to issues with your firewall settings, connection between your VMs and GydrusManager can be malfunctioning leading to VM Numbers being set to "-", which is not the desired behavior.
#### Solution ✅
In your host machine (server), go to **Windows Defender Firewall with Advanced Security.**
* Click on Inbound Rules, left hand side.
* Look for the rule withe name "GydrusManager (API)" and double click it to access its properties.
* Go to Advanced.
* Make sure that in Profiles, both *Private* and *Public* are **checked**.
VMs will start to have correct VM Numbers after they finish their matches, nothing else is needed to do at this point.
### VMs don't have internet connection
This issue usually happens on home servers with a lot of VMs running, it seems no matter what you do, you can't seem to establish an internet connection in them.
This is a VMWare IP address leasing issue, to fix it do the following:
* In VMWare program, click on **Edit**.
* Click on **Virtual Network Edit**.
* Once there, select the network with type **NAT.**
* Go to the **Subnet IP** textbox and change the third octect of the IP address, in this case the number **204** for any other number from 0-255.
* Click on **OK**.
Issue is fixed, VMs should have internet now and no restart or other step is needed.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.gydrus.net/general-information/best-practices-and-common-issues.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.