Hi,

I am seemingly getting the following error and have debuged and fully worked out the cause for it.
Internal Exception: java.io.IOException: Error while write(...): Connection reset by peer

Anytime some one connects to the server that has the '*' permission they are kicked with this message. I believe the bit that connects them is when a call to hasPermission is used, but I cannot confirm that. Regardless, it is a lot of work to find every single permission I node I need to give.

As seen in the config however, it appears that node.* still works.

Minecraft Version 1.11.2
Pex version: 1.23.4
Spigot - Latest build 1.11.2 11th February.

Pex config that failed:

groups:
  default:
    options:
      default: true
    permissions:
    - modifyworld.*
  LeadDeveloper:
    options:
      prefix: '&1[&3Hi&1]'
    permissions:
    - '*'
schema-version: 1
users:
  edcd76de-32ed-446f-ada9-42f1ea9c7d25:
    group:
    - LeadDeveloper
    options:
      name: passy999

Hopefully this helps.

I cannot copy the full log for security purposes, however I will give you a snippet of all the permissions ex related outputs.

[05:33:33] [Server thread/INFO]: [PermissionsEx] Loading PermissionsEx v1.23.4
[05:33:33] [Server thread/WARN]: [PermissionsEx] This server is in offline mode. Unless this server is configured to integrate with a supported proxy (see http://dft.ba/-8ous), UUIDs *may not be stable*!
[05:33:39] [Server thread/INFO]: [NametagEdit] Enabling NametagEdit v4.1.2
[05:33:39] [Server thread/INFO]: [NametagEdit] Found PermissionsEx! Hooking in.
[05:33:39] [Server thread/INFO]: [PermissionsEx] Enabling PermissionsEx v1.23.4
[05:33:39] [Server thread/INFO]: [PermissionsEx] Initializing file backend
[05:33:39] [Server thread/INFO]: [PermissionsEx] Permissions file successfully reloaded
[05:33:39] [Server thread/INFO]: WEPIF: PermissionsEx detected! Using PermissionsEx for permissions.
[05:33:52] [User Authenticator #1/INFO]: UUID of player passy999 is edcd76de-32ed-446f-ada9-42f1ea9c7d25
[05:33:52] [Server thread/INFO]: passy999 has join tasks.
[05:33:52] [Server thread/INFO]: [VanishNoPacket] passy999 disappeared.
[05:33:52] [Server thread/INFO]: passy999[/122.149.142.126:53641] logged in with entity id 199 at ([world]-18.0, 117.0, 24.0)
[05:33:52] [Server thread/INFO]: passy999 lost connection: Internal Exception: java.io.IOException: Error while write(...): Connection reset by peer

http://pastebin.com/kjaEBZ6b for the permisisons file - Pastebin makes it look formatted wrong but the plaintext at the bottom appears right. There is no syntax issues.

Currently this pex is only setup to test against passy999 however I have also additionally tested with myself Guru_Fraser however have excluded it here. This is within a server connected to bungeecord.

Bungeecord server. Yuck.

Unfortunately, you're going to have to talk to people from Bungeecord about how to set the server up correctly. PEX requires the server to be in online mode, Bungeecord does something to allow the server to be in offline mode, and I have no idea what Bungeecord does or how to set Bungee servers up since I've never used it.

@zml2008 may be able to tell you— he's the programmer for PEX; I'm just the official troubleshooter/guru for PEX 1.x.

Well its a server connected to bungeecord. However, this was working without issue up until I updated to 1.11.2 so I really don't know what would have changed in order to break this, I have not even changed PeX version since we're using the latest. @Stormbow

It may be an issue of Bungeecord not being compatible with 1.11.2 yet. Have you verified that it is?

The server works without issue without PeX. The server works for people not assigned to a specific group. Just when this scenario comes up it fails.

The problem is, you're not the first person to use Bungeecord and wildcards. I've seen other servers in the past few months that have used wildcards and haven't had this particular issue. That's what's got me confused about what's going on and why I wanted to see the full server log and permissions.yml file.

And— to be completely honest —in the past 4 years that I've been helping people with PEX issues, absolutely no one has ever had a "unique" server idea that I haven't seen from other people before them, so I hope you're not hiding your information for those reasons.

This is the first time I'm hearing about such an issue.

Let me see your full server startup log and permissions.yml file. (Pastebin)

Also, let me know which user this is happening to.

No I'm hiding server information because its custom code and not stuff that I should be sharing in public.

Aside from your super top secret custom plugins and other information being a potential source of the problem, I don't know what else to tell you.

Maybe @zml2008 will have a better idea of what could be going on here...

Unfortunately PermissionsEx is currently unmaintained and no further updates are planned. Because of this, all pull requests are being closed. If you are looking for an actively maintained permissions plugin, take a look at LuckPerms. It is compatible with major server platforms and can import data from PEX.