Netduma Fraser

Yes absolutely, we're working on it currently!

When you get an issue again can you check if the router is really hot on the underside please?

I've asked the dev if they can have a look hopefully they'll be able to have a look today.

There doesn't appear to be anything relating to the disconnect there, did you take it at the time?

Please upgrade back to the latest DumaOS you can, setup remote support, DMZ all that stuff to ensure you're accessible then post back here on your connection within the next 1h30mins and the dev should be able to take a look

Unplug the router for 10 minutes, plug it in, wait 2 minutes and then see if you are able to access it. Did you factory reset after uploading to that beta firmware?

I'll have to find out when abouts the dev will be available and then see if you can post then when connected to your broadband so he can try and access straight away as I think part of the problem is trying to connect too late

Heatmap would be just something we need to update - the server would still be there

No it doesn't unfortunately but I have already asked the team to update our OpenVPN version so hopefully they'll be able to do that sooner rather than later

Let us know how you get on! I don't think you've done anything wrong!

It won't be anything on our end, may just be less population size at that time and so less players across servers

Could you contact Nord please and see whether they can either amend the file or provide a file that will work with OpenVPN version 2.3.4 please?

Do they give you any more files than that or have a section for legacy OpenVPN?

Could you provide the config file you're using please?

Re-sync the Heatmap cloud and then it should appear for you

For some reason we're still unable to access you. What is the modem/router the R1 is connected to? Does it have a firewall you can disable?

The dev has asked to double check remote support is ticked and the R1 is in the DMZ of your modem if applicable and no port forwarding rules on the R1 itself. Let us know and then we should be able to access.

We get loads of PMs that's why we focus on support on the forum, I only have one PM from you saying you've sent some previously but I don't have those and I can't see any emails on the Netduma account if you used the email associated with your forum account? If you need anything in the future please make a topic and we can help out and reply much faster than PMs. Thanks for submitting IDs to the cloud form, we don't reply to anyone that has submitted IDs to the form or update them on when it is done, people submit them and when we're able to we put them in the cloud.

Well if you notice the Geo-Filter ping becoming higher or more unstable, Connection Benchmark results becoming worse despite no changes and then changing QoS to counteract it could be helpful

Not much we can do to troubleshoot/diagnose that unfortunately but if you find any stats that appear different that would be really helpful for us

Thank you for the feedback, that's an interesting observation, is the delay felt or is it seen in the Geo-Filter ping for example? What surface is the router on?

I meant the error could have happened due to deleting a device but reset is the go to fix for this currently

That could've been deleting the device itself and why a normal reset fixed it

It is quite possible restoring the config could cause that, especially if the IP address or name of the device changed which could also be contributing to it without restoring, we should be able to resolve that but it shouldn't appear to happen too often

So basically the error occurs when a device has been added to the Geo-Filter but that device then gets removed completely from the router for example so if you deleted it from the Device Manager but didn't remove it from the Geo-Filter is one cause. So yes likely the config is bringing back the device to the Geo-Filter but its not connected to the router. So a clean factory reset will fix it.