# Snowflake proxy NAT type changes to restricted on retest

**URL:** https://forum.torproject.org/t/snowflake-proxy-nat-type-changes-to-restricted-on-retest/15969
**Category:** Support
**Tags:** snowflake
**Created:** [November 24, 2024, 10:08am UTC](https://forum.torproject.org/t/snowflake-proxy-nat-type-changes-to-restricted-on-retest/15969 "2024-11-24T10:08:35Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![BobbyB](https://forum.torproject.org/user_avatar/forum.torproject.org/bobbyb/32/5456_2.png) [@BobbyB](https://forum.torproject.org/u/BobbyB)
#### Post date: [November 25, 2024, 12:11am UTC](https://forum.torproject.org/t/snowflake-proxy-nat-type-changes-to-restricted-on-retest/15969/2 "2024-11-25T00:11:22Z")

</div>

Did you see this post on my thread?

> [@Planning for my proxy as Unrestricted](https://forum.torproject.org/t/planning-for-my-proxy-as-unrestricted/15909/8):
>
> If the modem reboots i suggest restarting the snowflake process because the state will go again to unknown=restricted. At least this happens to my machines. If modem gets a new ip the users count drops to 5-10 from 80-120.

I also found that on a machine reboot the proxy never started properly because I guess the machine was not really ready with the networking part.

I put a 3 minute delay in the cron job for the reboot and that fixed it. Of course, as you know, I was not unrestricted yet and would not have noticed this.

---

_[View the full topic](https://forum.torproject.org/t/snowflake-proxy-nat-type-changes-to-restricted-on-retest/15969)._