Huawei just sounds like a sketchy company. I've heard that they pirate GitLab Enterprise edition

@IRJ said in MSP Helpdesk Options:

It's truly mind blowing how many ticketing systems are out there in the wild.

Tons of FOSS ones, but of there's a feature you want, it things the list a lot. Just wanting the concept of clients being under an organization and accepting tickets via email drops a ton of FOSS ticketing systems.

@scottalanmiller said in MSP Helpdesk Options:

Some open source project could do an amazing job with that really easily.

I've thought of creating an open source library for ticketing features, since at work we want to replace the email client we created and built in to the software with a ticketing system, but it's unlikely I get time to work on that during business hours.

Did someone ever test out Zammad or was there something to disqualify it? I remember it looked interesting.

Don't bother trying Jira Service Desk.

Last I heard, GitLab uses ZenDesk.

@wrx7m when you use domain roots in nginx it makes things a lot easier than if you go for a URL path.

@scottalanmiller said in Has anyone got a guide to installing ScreenConnect on Fedora 30 with Let's Encrypt?:

@flaxking said in Has anyone got a guide to installing ScreenConnect on Fedora 30 with Let's Encrypt?:

It's possible that it is simply the preference of their support team.

Which is what I assumed. A support team that goes out of their way to promote their preference. The product definitely works really well on Linux, so that it works great, and costs less without taking any money from them, means someone has to be pushing an agenda (likely personal) to get it on Linux.

Most obvious things are either a support team that feels Linux needs less support and that their jobs won't be needed, that lack basic support skills and Linux isn't something that they've been taught to support, or they just have fan boi problems like so many people in those positions do and are pushing a bizarre personal agenda for no personal benefit.

I'd go with #2. They're probably not well enough trained to be able to support actual production environments, and so they want to support installs that are in production use but not actually being treated like a production environment.

@scottalanmiller said in Has anyone got a guide to installing ScreenConnect on Fedora 30 with Let's Encrypt?:

@flaxking said in Has anyone got a guide to installing ScreenConnect on Fedora 30 with Let's Encrypt?:

@scottalanmiller said in Has anyone got a guide to installing ScreenConnect on Fedora 30 with Let's Encrypt?:

@flaxking said in Has anyone got a guide to installing ScreenConnect on Fedora 30 with Let's Encrypt?:

I've heard some bad reports about running screenconnect on Linux. Probably due to the fact it relies on Mono for .Net, rather than actually being initially developed for Linux.

No, the issue is more marketing than actual issues. We've run on both Windows and Linux and all things considered, it's been better on Linux. All the issues come from it being poorly written for legacy .NET and not updated to current .NET, but not really an issue. .NET itself is cross platform and no more Windows than Linux. But it's written for legacy, and needs Mono to deal with that, but Mono does so just fine.

But because of Nginx, SC is actually quite significantly better on Linux than on Windows. Lower cost, better performance (at the same price point.)

I think the issue I was thinking of was this one https://control.product.connectwise.com/communities/6/topics/1691-tls-13-seems-to-breaks-screenconnect-when-using-ssl-on-mono

So I think at this point reverse proxy ssl termination should probably be considered the best way to run it on Linux, which is pretty standard for a lot of web apps.

FTFY

Having SSL offloaded to a reverse proxy would be the expected way to run anything like this in production. If you aren't doing this on Windows, you aren't treating the Windows install as seriously as the Linux one. The expected deployment method for this on Windows would still be to have Nginx (or similar) in front of it, generally on Linux. So the parts that you are finding most challenging are identical regardless of how you install SC itself, the reverse proxy is equally standard, and equally likely to be on Linux.

That they have an issue with SSL on Mono is really neither here nor there. That's the wrong place for SSL termination to be. And I know people running SC on Windows that can't get SSL working too. It's not just a Mono issue, maybe a different issue, but SC support wasn't able to help. So they need Linux there, even for Windows installs. The SSL issue with Mono is like running something like NodeJS. You don't put SSL encryption in the app itself, you put it in front. Like you said, it's a standard pattern.

Good fix.

@scottalanmiller said in Has anyone got a guide to installing ScreenConnect on Fedora 30 with Let's Encrypt?:

@flaxking said in Has anyone got a guide to installing ScreenConnect on Fedora 30 with Let's Encrypt?:

I've never used Mono but from what I understand the later versions are on par with newer .Net

Mono is .NET, just an open source implementation of it. Mono isn't catching up with Microsoft's native .NET (although MS owns Mono I believe, so both are MS), but rather Microsoft long ago released their own .NET Core for Linux which is 100% identical to the one that they make for Windows. This modern .NET Core is cross platform and really, really good. Mono is only used for running legacy .NET code that isn't updated to Core and is Windows specific and never released for any other platform other than Windows by MS themselves (but is legacy and deprecated even on Windows.)

So the future of .NET on Linux is very bright, but not because Mono is improving, but because the need for it was eliminated.

Yeah, at our shop we would always call .Net Core by it's full name. By .Net I mean the "legacy" framework. I would have put .Net 4.5+, but I'm not 100% sure that's when full compatibily begins, but probably.

@scottalanmiller said in Has anyone got a guide to installing ScreenConnect on Fedora 30 with Let's Encrypt?:

@JaredBusch said in Has anyone got a guide to installing ScreenConnect on Fedora 30 with Let's Encrypt?:

Stop pushing your conspiracy theories without proof.

1. This shows a misunderstanding of what a conspiracy is.
2. The proof is in their software. There's gobs of proof. They 1) make crap that depends on legacy components and 2) go out of their way to push the Windows version when the Linux works really well and is easier to get working properly.

So neither a conspiracy, and loads of proof. Stop acting like it's crazy to point out the obvious.

Technical debt + starting using a Microsoft stack is a great way to vendor lock in without any kickbacks.
It's possible that it is simply the preference of their support team.

Hmm, I thought screenconnect was trying to wind down on premises sales, was I wrong or did they switch directions? A Mono update is a good sign. I've never used Mono but from what I understand the later versions are on par with newer .Net

@scottalanmiller said in Has anyone got a guide to installing ScreenConnect on Fedora 30 with Let's Encrypt?:

@flaxking said in Has anyone got a guide to installing ScreenConnect on Fedora 30 with Let's Encrypt?:

I've heard some bad reports about running screenconnect on Linux. Probably due to the fact it relies on Mono for .Net, rather than actually being initially developed for Linux.

No, the issue is more marketing than actual issues. We've run on both Windows and Linux and all things considered, it's been better on Linux. All the issues come from it being poorly written for legacy .NET and not updated to current .NET, but not really an issue. .NET itself is cross platform and no more Windows than Linux. But it's written for legacy, and needs Mono to deal with that, but Mono does so just fine.

But because of Nginx, SC is actually quite significantly better on Linux than on Windows. Lower cost, better performance (at the same price point.)

I think the issue I was thinking of was this one https://control.product.connectwise.com/communities/6/topics/1691-tls-13-seems-to-breaks-screenconnect-when-using-ssl-on-mono

So I think at this point reverse proxy ssl termination should probably be considered the best way to run it on Linux, which is pretty standard for a lot of web apps.

@Scott

It's just the web portal that's not encrypted without an ssl certificate, so it depends on how you're using screenconnect to determine what kind of risk that is.

People probably use nginx for the ssl termination instead in order to use Let's Encrypt.

I've heard some bad reports about running screenconnect on Linux. Probably due to the fact it relies on Mono for .Net, rather than actually being initially developed for Linux.

DNS round robin for failover kind of works, but it's not the greatest solution. We use it for our nginx proxies.
It relies on the application to move on to the second IP address if the first one times out.
But I think the client DNS cache just stores 1 IP address, so you need a low TTL, because if one proxy goes down, clients that have that IP cached will lose access until they do a new DNS lookup.

Django popularity seems to have skyrocketed in the past couple of years. Python being just an all around popular language has probably helped that.

@IRJ said in Starting a job search:

@flaxking said in Starting a job search:

I'm not planning on moving, so the position would have to be a remote one. I'm looking for an IT or a Development job, or some combination of the two.

That's pretty damn broad. What skills do you have to offer on your resume? What certs or experience do you have in DevOps roles?

C#, Python, Powershell, Nginx, IIS, Docker, Jira admin, Windows sysadmin stuff

I'm kinda in a DevOps-type role right now, but most of the time I either work on IT stuff or Dev stuff and don't get much time to work with the DevOps tools (which means that no one is working on it).
I only have real professional experience with CruiseControl, though I've done some working with Jenkins, Bamboo, Azure DevOps, and GitLab. Our Docker Swarm project was deprioritized, so I don't have any production experience there. If I was going to try to go full speed into DevOps, I would probably try to get a Kubernetes certification. The last certification I got was MSCA Windows Server 2012. There's a demand for DevOps-type roles, but actually getting one looks like it would be challenging, it seems like often they're looking for someone with a good amount of experience with a software stack similar to what the company is using.

If I wanted to focus on CloudOps, I'd probably focus on Azure since I've already have a bit of a head start there with things I've worked on in my current job.

Evolution didn't actually include the email data in the log, so that's where the SMTP commands I ran could have differed

I ran Evolution in debug mode, the email sent, then I tried to run the same SMTP commands as in the debug log in telnet but got the error again

Hmm, I just got the same when testing using telnet

550 5.7.1 Non-Compliant sender address. Code : -4