05:09 <AshW> Hello, is there someone around by chance?

05:09 <ocdtrekkie> Usually we're somewhere!

05:10 <ocdtrekkie> Hi how can we help?

05:10 <AshW> Hi there! I'm a bit of a newb when it comes to this kind of thing, and I'm having trouble with my install. I'm on CentOS 7. I had a polkit error that I believe I fixed, but I'm still getting a listening error

05:11 <AshW> in addition, it doesn't seem to want to send an error report in either, so I'm a little puzzled

05:12 <ocdtrekkie> Our error reporting in the installer is not active, as the case is.

05:12 <AshW> Ah, I see

05:12 <ocdtrekkie> Either we'll fix it or remove it soonish, but that one isn't your issue.

05:12 <AshW> No, you're right, haha

05:13 <ocdtrekkie> What error are you seeing and when do you see it?

05:15 <AshW> I'm seeing:

05:15 <AshW> *** Uncaught exception ***

05:15 <AshW> sandstorm/run-bundle.c++:1874: failed: bind(sockFd, reinterpret_cast<sockaddr *>(&sa), sizeof(sockaddr_in)): Address already in use

05:15 <AshW> stack: 61cb24 61b285 61a25f 619a3c 4965c7 4961a4

05:17 <ocdtrekkie> I think that means there's already something using the port you're trying to put Sandstorm on, maybe?

05:17 <ocdtrekkie> (I am the least Linux-inclined who frequents here, fwiw, we have experts, I am just not one.)

05:18 <AshW> yeah... I got there, though. The SMTP port that sandstorm is looking for is 30025 by default now, but when I checked netstat, I didn't see anything that was getting in the way

05:19 <AshW> I could be checking in the wrong spot, though

05:19 <AshW> or not be looking in the right way

05:23 <ocdtrekkie> So nothing on like, 80, 443, 6080, or 6081 on this box?

05:24 <AshW> 80, yes, the rest, no

05:25 <AshW> 80 is held by httpd which is apache

05:25 <ocdtrekkie> Did the install complete before you got this error? I'm wondering if we can see what ports are in /opt/sandstorm/sandstorm.conf

05:26 <AshW> it hasn't completed, no--it fails out each time. I've tried about ... four times now? The first several times I was getting polkit errors, but most/all the files deposit into the respective folders and my *.sandcat.io subdomain gets grabbed.

05:26 <ocdtrekkie> Because if you're going to use HTTPS, we don't really need 80, we just need to make sure Sandstorm tries to use something else.

05:27 <AshW> which means there are now... three duplicates of that, and I'll have to ask for those be deleted probably whenever I get this working

05:27 <AshW> I will be using HTTPS, but this is a brand new VPS, so I'm still getting it set up

05:27 <AshW> so I am actually doing letsencrypt right now

05:28 <AshW> --at least as far as I understand how this works, anyway

05:29 <ocdtrekkie> Sandstorm can basically manage Let's Encrypt for you, provided we get it installed.

05:31 <AshW> that would be wonderful. I have CWP installed, as I'm used to CPanel and that's been helpful for me visually. I don't want a self-signed certificate, as everything I want to install is grumpy when I do that

05:32 <AshW> letsencrypt just yelled at me for not having a virtualhost for my primary domain name, so I'm making a .conf file for that (learning)

05:32 <ocdtrekkie> So either we should be able to find a path for the installer where we can make sure it doesn't use port 80, not sure what options you set there in the script, or maybe we can stop Apache, install Sandstorm, fix our Sandstorm config to not use 80, and then restart Apache?

05:33 <ocdtrekkie> Not sure what you're using Apache for. Generally we do recommend letting Sandstorm pretty much be the whole box, but it definitely doesn't require it.

05:34 <AshW> frankly it might not work with the web panel if I'm understanding you right, I thought it might be alright, but it may vie for the same things that CWP does

05:36 <AshW> so this was still helpful, I may be trying to make it do something that it's not meant for

05:37 <ocdtrekkie> Well, it depends what you're hoping for. If you want both your web panel and Sandstorm to use https/port 443 eventually, you're going to need a bit more custom of a setup.

05:37 <ocdtrekkie> People have written some tutorials on it in the past. It's all doable, it just depends on your comfort level.

05:38 <AshW> That's fair. I was primarily interested in the app market that Sandstorm offers, and I'm interested--it just depends on how much of a headache and "this really wasn't meant to do that" it is

05:39 <ocdtrekkie> https://docs.sandstorm.io/en/latest/administering/sniproxy/ <- this is the docs on how to share your HTTPS port, essentially.

05:39 <AshW> I'm an artist. GUIs and visual aids are really helpful, so I'm really glad that this exists frankly!

05:39 <AshW> I'll take a look

05:40 <AshW> thank you! let's see where this goes

05:40 <ocdtrekkie> What are you getting from CWP? I don't know what it is.

05:41 <AshW> it's a full web/server management panel that operates in place of paid services like cPanel

05:41 <AshW> so it allows me to easily create users, add domains, etc

05:42 <ocdtrekkie> Ah okay. I've used a lot of cPanel since like 2003 to now. I'm actually trying to move the stuff from my cPanel based hosting into Sandstorm.

05:42 <ocdtrekkie> There are scenarios where Sandstorm does this well and scenarios where Sandstorm does not do this well, and I will be doing some very bad hacks to make it happen in my case.

05:43 <AshW> I see, lol

05:43 <AshW> I'm testing to see if I need something AS complete as CWP or if I'd be happier with something a little lighter, but allows me to still manage users

05:44 <ocdtrekkie> Sandstorm's preferred way of hosting public websites only allows static content hosting, which is very secure and such. If you want to host dynamic sites on Sandstorm you have to do unsupported things and you almost certainly torch SEO-ability trying.

05:45 <AshW> that's interesting

05:45 <AshW> okay

05:45 <AshW> It may just not be the right fit for what I'm looking to do right now

05:45 <ocdtrekkie> But I'd probably recommend Sandstorm for internal-use apps amongst your users, and probably something like CWP for public website hosting.

05:46 <AshW> that would be the ideal solution

05:46 <ocdtrekkie> We should be able to get Sandstorm running for you on other ports, depending how comfortable you are with the address being weird, so it doesn't run afoul of CWP

05:47 <ocdtrekkie> Do you have an /opt/sandstorm/sandstorm.conf file on your server? I'm wondering if the install finished more or less but the server just couldn't start.

05:48 <AshW> I'm fine with weird a la a couple folders deep or subdomain'ed

05:48 <AshW> I do have that file

05:49 <ocdtrekkie> So if you cat /opt/sandstorm/sandstorm.conf, is port 80 on one of the lines?

05:50 <AshW> I will have to check for you shortly, in the middle of another set of processes for prepping sniproxy:)

05:50 <ocdtrekkie> okay no problem

05:51 <ocdtrekkie> note that if you get stuck with sniproxy struggles, you may need to hope someone else drops into the convo to help. I have definitely never done that setup myself.

05:51 <AshW> oh, yeah. "PORT=80"

05:52 <AshW> *mechanic voice* there's yer problem

05:53 <AshW> I can change that, but should probably consult/review what a good port will be re: my netstat list

05:53 <ocdtrekkie> So if you set that to 6080, and sudo sandstorm restart, it'll probably boot up. 6080 is a Sandstorm preferred one, nothing too common uses it usually.

05:54 <AshW> sweet. let's see if I can boot it.

05:54 <ocdtrekkie> Depending on your sniproxy config you may want to also change HTTPS_PORT to something else too. That tutorial suggests 7443 I think, but again, you can change it later.

05:55 <ocdtrekkie> If the server starts, you should be able to run I think "sandstorm admin-token" to get a one-time code to get into the web UI and continue setup.

05:55 <ocdtrekkie> Might need to sudo that too.

05:56 <ocdtrekkie> For the record, I'm a Windows IT admin at heart, so outside of the very specific Sandstorm things I do... I guess a lot.

05:57 <AshW> that's cool:)

05:58 <AshW> to be honest I haven't been able to get it start up after a failed install, so I'm a little lost re: getting it running

06:04 <ocdtrekkie> So you changed the HTTP PORT to 6080, and did sudo sandstorm start and got an error?

06:06 <AshW> checking now

06:06 <AshW> no error, just no start either

06:07 <ocdtrekkie> Hmmm... wondering if we should have you remove and reinstall it again, but I'd have to see what installer options would let you set everything right the first time.

06:08 <AshW> I can do that. I would need to follow the manual install procedure though, you're right

06:13 <ocdtrekkie> Depending on your comfort level with it, we could also try to set up some sort of screen share to troubleshoot it.

06:15 <ocdtrekkie> I think you might be able to do like install.sh -p 6080 to force it to not use port 80 when installing. It might fail to do HTTPS setup then, but that is definitely part of it we can fix later.

06:16 <AshW> I'm open to that, I just need to step away for a few minutes

06:17 <ocdtrekkie> No problem, I'll be around a while yet, and most other days.

06:17 <AshW> thanks!

06:41 <AshW> alright, I'm back. Interesting news. Still didn't finish installing, but the -p 6080 moved it further

06:41 <AshW> ERROR: connect(): No such file or directory; address = unix:/opt/sandstorm/var/sandstorm/socket/shell-cli

06:41 <AshW> There might be more information in: /opt/sandstorm/var/log/sandstorm.log

06:41 <AshW> *** INSTALLATION FAILED ***

06:42 <AshW> getting the log now

06:42 <AshW> I don't think the log updated, this looks like the same error from earlier. I should have snagged the timestamp for confirmation

06:43 <AshW> i.e.

06:43 <AshW>  ** Starting Sandstorm at: Thu Aug 4 06:29:46 2022

06:43 <AshW> *** Uncaught exception ***

06:43 <AshW> sandstorm/run-bundle.c++:1874: failed: bind(sockFd, reinterpret_cast<sockaddr *>(&sa), sizeof(sockaddr_in)): Address already in use

06:43 <AshW> stack: 61cb24 61b285 61a25f 619a3c 4965c7 4961a4

06:44 <ocdtrekkie> I'm wondering if we should just have you sudo systemctl stop apache2, install Sandstorm, make sure it runs, then swap the ports around, restart it, then reenable Apache?

06:45 <AshW> it might be the best call. I may have to put a hold on it after all, it's almost midnight here and I'm starting to run out of steam

06:47 <AshW> thank you for your help so far, though, it's been a learning experience regardless!

06:47 <AshW> I'll probably be back in the morning my time at some point

21:05 <ocdtrekkie> Just tested out having a GitHub action sync a GitWeb grain every time I push anything to one of my repos.

21:05 <ocdtrekkie> I might start doing it as a general practice because it's effortless enough, and grants me a local copy of everything while being lazy.