Netduma Fraser

Added

There isn't a logout function on DumaOS 4 currently

We haven't specifically tested the game so while it can work, it's not optimized for it. It's likely in both cases that it is trying to connect to a server outside your radius, in terms of the chat, if you disable it once you've forced a server then it should allow you to chat, then you can re-enable it once it's working and you should then be able to continue filtering from then on and the chat should hopefully continue working. Probably the best solution though is if you see a blocked icon on the map (zoom out) when you're playing, add it to your allow list and it should work then - you may need to do it a few times, there is likely multiple servers for it.

You already have access: https://forum.netduma.com/forum/151-netduma-r3-early-access/

Yeah it's a London cluster that has been whitelisted by mistake, it's being rectified currently

You have to be signed in to view it, are you doing that?

You ask them for the OpenVPN configuration files or specifically ask for the OpenVPN config files for whatever server it is you want to connect to. You should have your username/password credentials already when you sign up.

It's the relay servers they're using causing it, we will look into it but may be no proper fix. Geo-Latency on the DumaOS 4 beta is the only thing that may make it happen less.

Added

As long as they provide you with the OpenVPN configuration files to connect to them then yes they should work

What do you mean by wrong server? What do you see on the map when you're in a match?

Is it that you're not getting a game or you're not seeing one within your radius?

Added

Go to the main forum and look in the testing section at the top and you should see if there, go in that way

Don't use the polygons, try with the normal radius instead

Added

You cannot set a ping on the Geo-Filter and expect to get a game at that ping value unless you know and have connected to games before where you've had that ping or lower - have you had that happen before? Also keep in mind due to the time of year servers will be under more strain and so the ping can rise. Can you provide a screenshot of how you have the Geo-Filter page please?

First thing to check if it's never happened before and the only thing that has changed is the DNS then disable nextdns and then check. If it still doesn't work then disable the Geo-Filter, does it work then?

It is generally that color scheme, should be able to see the circle lines within it though, I can't tell if that's there or not from your photo but won't affect functionality.

The internal tool has been fixed so we can fix the cloud issue, I'm hoping it'll be done within the next few days

Sorry about that, please try again

I cannot know if you have set up everything correctly, that's what I have to determine. Where are you measuring these pings exactly? If you don't want to troubleshoot that's fine but I can't give you an estimate or plans for something like an issue when I cannot be sure if said issue is legitimate or not.

Please make a new topic for your issue and we can continue there. Though some routers are picky about the order in which they're booted, if that happens reboot your modem, wait 2 minutes then reboot the R3, wait 4 minutes then check for internet.

When you say system error do you actually mean you are getting an error or do you just mean it isn't working? An error is good, it's a message/information about what is happening and I can use that, if that's not happening then just say it's not working still. Could you attempt to enable RGB using the DumaOS mobile app please and see if it works then?

@DARKNESS Right logic but I think you're referring to the LAN IP for the XR and we want the WAN IP so it does have to be set within the given DHCP range of the Linksys. @ADhillon please let me know the answer to the below. Also following the above logic, access the Linksys interface and find where it shows listed devices, you should see the XR1000 listed there. If you can reserve/set a static IP for it there then go ahead and do that. If not you should be able to find the option in LAN or DHCP settings, then give it the IP it's already showing you on the device list and save. Then see if the issue happens again.