
Does your Rust rental need more disk space or more memory?
Start with what failed at a known time. If the game ran out of room to write a backup, ask how to increase available storage. If the process stopped under a memory limit, ask about memory. Get the host to tell you which limit it saw when the evidence is unclear.
Put the symptom and the reading together
Open the console and the rental’s resource display. Match the time of the failure to the closest readings available. A full disk after a large save or archive points to a space problem. An abrupt exit while the host reports that the service exceeded its memory limit points to a need for more memory. A high reading by itself does not connect either limit to the failure.
| What you observed | Ask the host |
|---|---|
| The new save failed and the panel shows no free disk space | Which files count toward my disk limit, and can we raise that limit without increasing memory? |
| Rust exited during map load and the host confirmed it reached the memory limit | How much memory would this change add to my service, and would the existing disk and files stay in place? |
| Both graphs look high, but the console has a map download error | Can you confirm which resource limit was reached or whether I should start with the download? |
Find out what the change affects
A provider may sell compute and storage together, or let you change one separately. Ask whether the resize requires downtime, changes the address or prevents going back to the smaller service. If the increase needs a move or an interruption, keep a separate backup and set a time the community can use.
Name one check to repeat after the change. For more disk space, compare available space at the same point during the next backup and check that the game can still save afterward. For more memory, repeat the startup that previously failed and confirm the intended world opens. If the original error returns, give the host those two readings and times before asking for another resource change.