On HAP and RB750G install successfull, Wireguard works to OpenWRT. But on first reboot after setup, both routers are reset to default settings. Restore from backup are not succesfull, every time after restart are factory settings on both routers active.
Backup are used when the hardware and router os software are the same. You can try to export config and import all or if that fails, use part and part until it fails.
The Backups are prepared after first setup from this version. And of course from the same router, I’m not an rookie.
My experience with Mikrotik is over 10 years and I have 8 Routers in produvctive Environment and 4 in Lab.
With only 4 post here, its not easy to see 
Wow, great! Can we get in contact? I’m using VeryMobile by Wind, it works very well on smartphone, but on Chateau in LTE mode I get only Tx traffic not Rx one.
I tried to contact you, but the option is grayed.
If it only takes another day or two, I don’t see the harm in waiting until they get it fixed. It would be different if it delayed it for weeks.
7.1beta2 (2020-Aug-21 12:29)
I have seen this problem on my Chateau (V7.0.1). From time to time when I reboot this device, then device has no more configuration at all! (not even default).
When this happens, and I try to use backup file made before this reboot, it will not load that backup file (this file is then useless).
You then need to start all over again and go back to a backup file that is working…
So each time I need to power this device off, I hope and pray that when booting again it has still its config…!
Despite my optimistic signature message, I stopped doing anything on R7 for now and wait for some new release hopefully fixing some of the issues.
When you are in that situation, I would rather make a /export instead of a /system backup.
It is usually possible to import a /export even when this does not go as smooth as you may want.
You may need to remove certain lines, or at least make sure the config is really empty not even the dhcp client that the system likes to add by default.
Also at least in v6 there is an error in the /export of ipv6 that makes it impossible to import it, the sequence of commands is wrong.
But maybe you are not using ipv6, or maybe this error has been resolved in v7.
So … it is friday and still no new release
I am still using OpenWRT with DSA on MT7621 because
Ros 7.1b2 does not work with vlans on RB750gr3/RB760igs
Ros 6.x does not have Wireguard
so if i want both “feature” i need to use OpenWRT
any chance for new beta?
Is it possible to downgrade? I have that SSH issue on 7.1beta2 and beta3 after xmas is too late for me.
Run a /export and save it.
Use netinstall to install the router with 6.47.7 and restore the backup you made before you went to v7 beta.
Then use the /export to review any changes you made after going to the beta and that you now want to apply to your 6.47.7 install.
Hello everyone,
Just wanted to thank everyone for bringing the wireguard to the Mikrotik.
Of course, the work is still in progress and there are few (already addressed) bugs, but so far - so good. It works rock stable for me.
I’ve got a bounce server (Debian 10), publicly hosted on a static ip, and I can reach all my peers without any problems.
The only thing I’m still missing, or I was unable to figure it out, is the mikrotik discovery protocol (udp - 5678) over the bounce server.
Like I said, I can access the peers without any issues (webfig, winbox), but I can’t see the peers in the discovered neighbors list.
Anyone have any tips and tricks on how to get it to work?
Port is open when trying to reach it from the bounce server, so that’s good.
Thank you, and wish you all a wonderful weekend!
Best regards,
Dorian
I own the Chateau LTE12. I wouldnt use the beta otherwise. There is no download archive for beta versions I know of - so where to get a old beta release?
I just received the device this week 11.11. and it was shipped with 7.0beta6.
Go to https://mikrotik.com/download
CTRL + F for searching: Chateau and you discover it at ARM family
RMouseB and copy URL
https://download.mikrotik.com/routeros/7.1beta2/routeros-7.1beta2-arm.npk
and edit it to:
https://download.mikrotik.com/routeros/7.0beta5/routeros-7.0beta5-arm.npk ← WORK 
https://download.mikrotik.com/routeros/7.0beta6/routeros-7.0beta6-arm.npk ← NOT WORK
https://download.mikrotik.com/routeros/7.0beta7/routeros-7.0beta7-arm.npk ← WORK
https://download.mikrotik.com/routeros/7.0beta8/routeros-7.0beta8-arm.npk ← WORK
Thanks! I did not assume that they have “unprotected” Download-Links where I can simply modify the file-name and e.g. guess for the version! Works indeed!
Is this just wrong information or can there be a difference between routeros version and routerboard version?
Please study the difference between RouterOS version and firmware version. Firmware is the bootloader.
It was made confusing by having the same version on the bootloader as on a RouterOS (even when bootloader was not changed at all)
but still it is a different thing.
When you click “upgrade” in that screen it will upgrade the firmware to the same version as the currently running RouterOS.
But likely that will not change anything, as the firmware in v7.1beta2 is likely the same as in 7.0.beta6.
Thank you for the patient answer. I am still new to the Mikrotik universe (< 1 week) and I still not discovered all wiki and stuff yet. It just confused me, as I pressed the “Upgrade”-Button on that page - but nothing happened and after refreshing the page still the same information was displayed. But now after a reboot it shows the most current firmware. Still have to get used to the Mikrotik-way that is not very intuitive. But once you know - you know. 
Yes, it’s not intuitive at all since Mikrotik decided to use same version numbering for routerboot and ROS. Before that, routerboot had it’s own version number so it was easy to see if something changed or not and if it’s really worth updating it. But now they keep version numbers in sync with ROS, so you don’t really know if routerboot has to be updated or if only change is the version number. So you end up updating it just in case, wasting NAND writes of critical bootloader sector every time.
But it’s still perfectly safe to run older version of routerboot and not update it unless you experience some problems. If some fix or new feature depends on a new routerboot, it’s usually noted in the changelog.