Sébastien Julliand
Sébastien Julliand
@krethan feel free to open a PR from your fork, using a [closing keyword](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) for this issue so it get linked automatically.
Good thinking @krisbaehr , thanks! @chrjorgensen do you think we'd need `coalesce` for these two fields?
@kraudy can you share the content of your `~/.bashrc` file if you have one?
> @worksofliam @sebjulliand any other idea? The arch people say they didn't change anything :/ They always say that 😁 No other idea so far...what if you run `system "DSPLIBL"`...
The next release will help with the certificate generation, even though it seems odd that it disables a profile that was able to connect in the first place. If you...
At this point, since the new debug configuration process is out, you should try to clean it up and start from scratch. 1. Delete the `/QIBM/UserData/IBMiDebugService/certs` 2. Hove over your...
Re-Enable your user (ask the nearest friendly admin), and then connect. You'll need *ALLOBJ to configure the debug service though, so maybe an admin can help you out with that...
At this point, we can put the debug service configuration aside since `*ALLOBJ` is out of the question. What you need to do now is contact your sys admins so...
Are you able to connect to this IBM i using an external SSH client? (like PuTTY)
Not accepting the password doesn't sound so good to me. Unless you meant you connected through **SSH** from ACS (not **SSL** - that is just a mean of securing the...