First things first: you can always go back. A reset empties the device, and next to your script sits a rollback script that undoes exactly what it added. So you can afford to go looking.
I cannot reach the router any more
- Are you on the right port? If the port you are sitting on was put into a VLAN, you no longer get an address from the old range.
- Did you enable an offbridge port? Plug a laptop into that one. It deliberately stays out of the bridge and the VLANs.
- No offbridge port? Use WinBox and find the device by MAC address, which works without a matching IP.
- Nothing helps: reset with the button while it boots, and start again.
No internet
- Does the WAN port get an address? Check
/ip address printand/ip dhcp-client print. No address means the problem is upstream of the router: cable, modem, a VLAN on the WAN port, or PPPoE credentials. - Is the modem in bridge? If it is still routing, you are behind two layers of NAT. That often works, but port forwarding does not.
- Is PPPoE connected?
/interface pppoe-client printshows the status. A wrong password or the wrong VLAN are the usual causes. - Addresses fine, but no websites? That is usually DNS. Test with an address instead of a name.
Websites load halfway, or hang
The classic MTU problem. It almost always shows up with PPPoE or through a tunnel. Switch TCP MSS clamping on, leave the WAN MTU field empty unless your ISP asks otherwise, and do not block ICMP entirely: those messages are how the right packet size is found.
Wi-Fi is gone after upgrading to v7
Your device is probably running the other Wi-Fi package. Settings from v6 (/interface wireless) only work with the wireless package; with wifi-qcom-ac installed your networks are not shown while bridges and DHCP are still there. Install the right package from the Extra packages of exactly the same RouterOS version, reboot, and import the Wi-Fi lines after that. See From RouterOS v6 to v7.
A package refuses to install
- Version mismatch. The package has to be exactly the same version as RouterOS on the device. 7.24 next to 7.23.5 is ignored.
- No space. Check the free flash with
/system resource print. Clear old files first. - Wrong architecture. ARM, ARM64, MIPS: the package has to match your device.
A switch or access point is unreachable
- Does the device carry the management VLAN? If not, it has an address but you cannot get to it. It is the most common mistake, and the site check reports it.
- Is the port it hangs off a trunk? An access port only passes one VLAN.
- Is your own laptop in the management VLAN, or allowed in? With "management VLAN only" on, an ordinary desk deliberately cannot reach it.
VLANs are not doing what you meant
- Check that both ends of every cable know the same VLANs. Draw your cables on the board and the check tells you.
- An access port is untagged, a trunk is tagged. Untagged on two VLANs at once does not exist.
- On some switch chips, bridge VLAN filtering costs you hardware offload. The tool warns you on those models; it works, but slower.
The script errors while pasting
- Paste into the terminal, not into a script window, and paste it in one go.
- Did the very first line clash with something that is already there? Then the device was not empty. Reset and start again.
- No Wi-Fi menu on the device while the script has Wi-Fi lines? Then the Wi-Fi package is missing.
Still stuck
Let us know through the form or on Discord. Include your model, your RouterOS version, what you were trying to do and the error. With an /export hide-sensitive attached it is usually clear within one reply.