No one can marry tp no matter if OP or having the marry.tp permission.
No errors on console.

Mariage master v.1.29.13
Spigot for mc 1.11.2

Can you please provide me with more details.
is there any message (like that the player was teleported)? Do you have economy enabled?

• No message, just the generic insuficient permission message. And as I said, no error in console... :(
• I do have economy enabled.
  Sorry... what else can I say? It's very strange.

Permissions: true
VaultPermissions: true
No one can teleport, not even OP
Permission plugin: PEX
Vault permissions is enabled, however I don't use VaultPermissions. This is just on by default, it never gave any issues. I may disable it anyway.

• Most other marry commands don't work either, globally in all of the network. Same issue. No permission.
  Commands like marry kis and marry divorce do work. Also marrying is possible and showing the list of marry commands.

This sounds like the problem lays on the bungee side of the plugin. Do you have the plugin installed on your bungee cord server?
If so:
Are the commands that not work: chat (if enabled in the config), home (if enabled in the config), tp (if enabled in the config), reload and update? They should still be listed in the help.
Do you have any permission plugin on your BungeeCord? Is the permission setup still correct (maybe an update has changed or reset the permissions)?

Since this seems to be a problem with the permissions I would need some more details.
Is "Permissions" enabled in the plugin config?
Is "VaultPermissions" enabled in the plugin config?
Can OPs still teleport?
Which permission plugin are you using?
If you have "VaultPermissions" enabled, which version of Vault are you using?

On my single server (I don't have Bungee), we can do /marry tp without problems.

yyyyeeeah.... I just noticed somehow the default rank had negative permission"-marry.user" attatched... I don't think that's very good for basic commands functionality xD.
I will slowly step back and retrieve and close this ticket if that was the issue...

You see, I didn't imagine this could be the case, someone from my staff must have messed up the thing. Or maybe it was when we switched the server to network and migrated some world specific permissions to global.