@dafyre Thanks, testing now to see if it works (as expected).

And arguing about the word "critical".

Specifically

"Critical" means everything outside "critical" is OK from the sources. So it's like "critical" is even more a niche than "any" production usage. That's why I think this wording is not fit: every production load (ie in a company) makes sense. Hobbyist is clearly not related to "production", that's why "critical" word isn't needed here

Critical in the business sense, means I need support, supporting it yourself is not an option.

FFS

@travisdh1 did you have any luck debugging the timeout/failure?

I was able to download.

@scottalanmiller It's not. I changed after I posted this.

This issue is now resolved. I had to issue the command git checkout master before the standard upgrade process would work again.

@bnrstnr said in XO behind proxy or exposed directly?:

nly web server I wanted to use, would there be any benefit at all of using a reverse proxy instead of just forwarding 443 directly to XO?

Still it would help for security purposes.

@danp his installation is pre-service creation.

IMO time to rebuild and get current.

@scottalanmiller said in ESXi and Xen Orchestra - Licensing models that are eerily similar:

@brrabill just people who like beating horses.

Well that's just cruel.

@stacksofplates Nice!

Read this. especially if you're using the community version.

Here is the more in-depth explanation of the issue.

5.8.1 was release earlier today. My test build is failing, but haven't had time to dig in and find out why.

@stacksofplates said in A script to pull updates from GH or use History:

@DustinB3403 said in A script to pull updates from GH or use History:

So to clarify here, the goal is to allow admins an easy way to pull the most current update script. Not to run it for them on a set schedule.

(reason being is if we auto-force an update, and that update breaks their system, I don't want to have that on my mind)

I don't understand the hangup here. The cron job I pasted above does not update anything. It doesn't run any scripts. It doesn't force anything. Where this is coming from I have no idea.

This is from sidebar conversations regarding the topic. It has nothing to do with the cron job you posted.

Maybe a new guide for a how to do a clean install and then how to upgrade 🙂 on Ubuntu/CentOS/Debian 🙂

@junaidmehmood take a screenshot of your XOA webpage so I can verify some things.

Just finalizing the conversation here that we feel pretty confident in the changes we've made to the update script.

You can update by downloading a new copy of the script or manually making the changes to the file.

The script will now reset any custom git changes that don't match the source, then the script will proceed, and make the necessary changes to enable the feature so you can import your config files.

@Danp a distro upgrade would likely be the easier approach. I'm performing this now on my system.

(first day back to work in 11-days!)