@RaRu 

This is basicly the different to the nas its config file and that from omada, he left (NAS) works, i also tried with removing that word no behind comp-lzo perhaps i just need to remove that whole line as stated on google:
27 mrt 2024 — To signal this clearly, --comp-lzo and --compress are discouraged and considered deprecated features

EDIT removed comp lzo in total and its just dont wane to connect :(

  @IIIdefconIII 

Do you have any port forwarding set up on your TP-Link?

Do you have anything in DMZ?

  @IIIdefconIII 

ohw i acutally have DMZ on my home assistant VM on as it seems but thats another network som im note sure if thats related, ow i just see my own anser, its unrelated because the network is completely disabled, all other networks has no dmz enabled, cause out of security reasons i dont think thats a good idea.

  @IIIdefconIII 

Hi,

Hard to say (for me) where is the issue.

I would start with disabling all port forwardings / DMZ / other VPNs settings enabled on that setup to keep only the OpenVPN server up and running.

Maybe some configuration is messing around with other settings and that's why it doesn't work.

I do use OpenVPN server on my ER707 as well as ER706W and in both cases it is working without any issue with all clients: Windows, iOS and Android.

Best Regards

RR

  @RaRu 
Ok so i disabled the 1194 NAS port to make sure its not going to bit each other:

As you can see in the same list above eht dms profile is already disabled.

Redownloaded the generated opvn file and remmove "no"

it asks for creds:

 

which i specify setup in omada itself:

 

it seems its not responding at all,

Gonne try this now brb/edit this memo

also disabled the vpn_out vpn profile

Keeps trying to connect Waiting for server.

  @IIIdefconIII 

disable port forward to 1195, you should not port forward when the OpenVPN server is on the Omada router.

  @MR.S  

Now im getting this after disabling it i Might need a new config let me double check that. even changed to config file to 1194 where the nas did work on and even tried it without any port number in the config. it doesn't make sense to close the part in the NAT rule right? 

 

  @IIIdefconIII 

In the config file you prepare, you need to have the same PORT as you set in server configuration.

You don't forward the port of VPN server since the connection goes to the router itself, so there's no need to set rule informing router what to do with that incoming connection.

Make sure you have the config and server set up properly. Make sure that the VPN user is assigned to proper VPN server.

After that you may want to reboot TP-Link router - you do a lot of changes in it's config recently, it may be a good idea to reboot it to clear it's memory and config a little bit :)

Best Regards

RR

  @RaRu 

After that you may want to reboot TP-Link router - you do a lot of changes in it's config recently, it may be a good idea to reboot it to clear it's memory and config a little bit :)

That makes totally sense thanks for biting in this apple for me, appreciate you commitment trying to help this broken nerd.

Currently:

Perhaps, if possible we can, if you want and can, have a remote sessions by either vpn, discord call or even teams, i think thats faster for saving u time helping me>>
Btw perhaps a moderator can cheer up the thread name instead of can we continue this conversation, the previous ticket got closed so i was going for a new try te get it working, yet im still stuck haha probably a PEBKAC

  @IIIdefconIII 

Hi,

I've sent you a DM.

Cheers