shiobi

It's possible that you're using a different PHP version/install on command line to the web server. It would be worth checking that /usr/bin/php is the right executable.

Bingo! That was it. Web server was using 8.0.19 and the CLI was using 8.1. I updated the CLI to use 8.0 and the maintenance script ran without error. 
Thank you both @Stuart Silvester and @Jim M

Developers have been tagged to see if there is anything further we can think of here, but unfortunately with it being server related, and a test site, there is only so much we can do in terms of support there

I've tagged our developers to see if they have any idea of what might be happening here. You dont seem to be getting any fail (wrong password etc) its just not logging in. It can only really be something server side there unfortunately

Is this your Test URL which you're having issues logging in with? Please disable CloudFlare for the time being to see if it is having any impact. I keep seeing IP address conflicts when attempting to login.

Hi @shiobi,
I have moved this topic to Help & Support as requested.
I assume you haven't you had any luck after getting in touch with another client above?

Would love to know what the issue was once resolved 👍

Please check your conf_global.php file, and ensure if you are using https on the server, you also have your address set to https there. If thats not the cause, please update your access details on file for the new server, and we can get this looked into

This issue has been resolved in 4.6.10 beta 1. Feel free to give this a try, or await the full release if you prefer

🤦🏻‍♂️
🤦🏻‍♂️🤦🏻‍♂️

Sure? On here it is ok after new year but not before…

I can confirm this on my sites as well..

On taking a closer look at this, it is indeed correct. There is no way in which to exclude these at present. It will show similar content from anything which is indexed in the search index. That would indeed include statuses

If you could update your access details on file, and indeed send me details of items on your site I can look at.

Another example:

Hi. For some time (at least for me), Google has started displaying the image on the right in search results on the desktop. 

I admit that it looks cool except that it does not work with the Invision Community 😞 Google apparently does not want to download the same image as the user's avatar over and over again.
Is there any hope that IC will add a feature for fetching an image from a topic? e.g. from the first post it is in.
You can use such an image to the meta tag "og" and to the JSON Schema Markup.
<script type='application/ld+json'> { "name": "Categories for Achievement Badges", "dateCreated": "2021-12-05T09:01:10+0100", "image": "//dne4i5cb88590.cloudfront.net/invisionpower-com/monthly_2020_09/NsG6U3vvlXU.thumb.jpg.d4b05c4699294571e9837b00bbfa3eb6.jpg", <meta property="og:image" content="https://dne4i5cb88590.cloudfront.net/invisionpower-com/monthly_2019_09/og.jpg.5e6c57e8dfa140ce4ac18f1e757d3b45.jpg">

More observant than me in a morning, clearly 🙂 
 

Hi,
Thank you for letting us know, we'll get that fixed in an upcoming release.

"41.27%" progress should fill up a bit more of the progress bar...

I've already canceled the self-hosted license because of the open forum support policy. The ONLY reason I have not canceled my Cloud license is proper ticket support is continuing.
For me it's basic principle. I pay for a product. I expect proper, private support for that product from the company with whom I have a business relationship. No one else. It is not my responsibility to create a living knowledge base, nor contribute to it. I have no interest in being part of a "community". I am a customer. That's it. That's the end of the relationship I want, and need, with IPB.
It's crazy that I've posted more times in this thread than I have in 17 years.
Suffice it to say, should ticket support end with Cloud, so will my license for it.

Hello!
Sorry for my translation, I use a translator. 🤗 But I can't help but speak out about the price increase.
I tried to use licensed software and therefore acquired a license, and all these years I paid for support, receiving updates, often not seeing any sense in them both for the community and for myself. My community is not a commercial one, we are a fishing community.
The news with an increase in prices hit us, the amount of $ 250 is not acceptable for us, given the number of support requests for the entire period of using the IPS.
But in the current circumstances, we most likely will not extend support, but perhaps we will start looking for an alternative engine. Or we will work as much as possible on the version that will be the last paid subscription for us.
Thanks to the developers for many years of work, but unfortunately, I will not be able to pay tribute to my habits in the future.

I have been a big fan of IPB all growing up, I was an admin on many forums using it in the past, and when I was younger and wanted my own sites (without being able to afford enterprise software), I even opted for InvisionFree.  With that being said, when my community moved away from MyBB in 2019, Invision Community was the obvious choice for me; we're entirely ran on donations, but I was willing to save up and pay for the price out of pocket because I was looking forward to an enterprise solution.
I talked up Invision Community on my forums, and while we were a bit bitter over losing BBCode (we're still dealing with posts with formatting issues in my community after all this time), we sucked up and made the migration (which unfortunately didn't go smoothly due to a bug with the MyBB conversion system, but a support ticket pulled through!).
I'm not upset about the price increase, though I think it could have been dealt with better tact (read on), but I'm pretty upset about the loss of opening support tickets.  Most of my tickets that I opened were legitimate bugs that had to be escalated to the devs, and some of them involved bugs that could have been security issues (e.g. seeing topics and posts in feeds under specific circumstances that were meant for only staff).  One of my biggest talking points to the community, and one of the biggest brags that I've done post IC was "The benefit of enterprise level software is enterprise level support!"  I could tell my community when something went wrong "I opened a ticket".  I can't do that now, and raising the price while removing that feels less premium.  Less enterprise level support.
Regarding Devs....  I'm presently terrified that this is going to lose people like @Adriano Faria.  @Matt I hope you're listening, because Andriano Faria is the reason we choose Invision Community.  Due to some specific nature of my community, being able to post between multiple accounts was vital, and without their Linked Accounts plugin, we would not have chosen this platform.  If it breaks, we won't be able to continue using it, as it was one of two mandatory requirements for a community platform (even Youtube allows me to switch between pre-selected linked accounts from a user interface, many people support this out of the box):
 
 I would pay for this 20 times over if it stayed (just not all at once!)
@Matt, earlier you listed a fair bit of features that were pushed in the last couple years; however, there's so many missing features that should be de-facto (and they are in other free solutions, e.g. MyBB, SMF, etc.) but have either been removed or haven't been included and require a plugin and some of these plugins are holding the software up.  People have been asking for night mode since 2019 for the main site (ACP is appreciated but only admins can see that), profile-specific permissions prevent 1-post spambots from joining and putting things in the website field (again, we needed Adriano Faria's plugin), searching reported content is pretty important for larger communities (plugin), bookmarks (plugin...still can't use it in the latest version), post number in thread ( @All Astronauts's Kitchen Sink took up that mantle when Tom Irons' left).  You cannot lose any more of these individuals; hire them to implement these things into the main suite if you have too, because it feels like these common sense features are simply not there when they should be.
As for the marketplace, it has burned me a couple times now, specifically with themes.  After upgrading my site's main third party, purchased, theme (which I only needed because Invision Community doesn't support dark theme natively), I shortly realized that there was a critical bug in it.  The author was prompt in giving me an updated xml with the fix, but since I already had linked the theme to Invision Community, I couldn't just upload the XML, and waiting for the theme to be approved was not immediate; my only choice was to create a brand new theme from that XML, which sucked because the theme in question was heavily customized 😞
The second time is still ongoing, since y'all rejected @Fosters' recent bookmark update (I understand that you're aiming for quality control here, but from what I've heard it can take weeks for the plugin to be in review).
As for as how this all could have been handled, it's unreasonable to never increase the price for existing users, and only introduce it for those coming.  However, it is also unreasonable to drop it on us with no prior report.  I remember when Flickr changed their pricing structure, and while it got some pushback, they not only provided a warning, but also allowed current customers to prepay another 1-3 years at the current rate before they did.  The result?  I bought 3 years worth at the old rate, and I think a lot of people did.
I think a better approach to this would be to give existing customers an additional year of the old pricing (or even just 2 more billing cycles), while bringing new ones in, but in this case even the controversial way that Flickr handled their increase I feel was more graceful than Invision Community's.
As others have said, there's still time to make this right; find a way to remedy this to show the community that you're still acting in good faith.  Let us open tickets if something is broken, but perhaps still allow "how do I do xyz" to be topics.
And please, I don't want to tell my members that we need to switch to yet another platform after arguing for this software for the past 2 years because you pushed away the developers... find a way to lesson the blow to them, or just hire them outright so they can bring these much-needed features to Invision Community (see above).
 
P.S. Also please don't make this software become another Discourse-like platform, another reason I love IPB is because it's always had the forums feel; I don't want to lose the bulletin board look.

As a long time user of approaching 20 years who has been a customer since the Ikonboard days and has a first recorded invoice here in 2005 for "Purchase: Invision Power Board Perpetual License".
For what it is worth, here is my feedback on the e-mail I received about the price hike and reduction in support levels.
Six years ago you contacted me as a "lifetime" member to tell me that the lifetime agreement I signed up for, which helped set the the financial foundation of these forums, was to be replaced with an annual fee. It was nice to get a little credit on account by way of apology, however, I bought a lifetime licence and it should have been for lifetime. Offering a lifetime licence is a marketing incentive, and not something that should be reneged on further down the line once a company has reaped the benefits of the marketing drive. Telling customers its one payment for lifetime access, then changing the goal posts to an annual fee is not the type of thing that reflects well.  
Onto the new e-mail....
Forums: was $50, now $80 (increase of $2.50/month) The marketing team really earned their wage this campaign as $2.50 doesn't sound like much, however this represents a 60% price hike from $50 to $80.
A 60% price hike needs to be backed up with some serious upsides.... however...
For most customers, support is simply “how do I do this?” and these questions tend to be quite similar. Rarely, support questions are “this went wrong” Not my experience. My support experience is basically the same every year - my forums go offline with errors every time I do an upgrade. It fills me with dread every year or so, and true enough I need to submit a ticket to try and get the forums back online. To think that that base line support for a quick turnaround on outages is either now reliant on an additional payment for a support plan, or posting in publicly accessible forums is not a sustainable proposition for me.
Creating a strong support community backed by our support technicians will result in a more detailed and richer set of answers For "how to I customise this" or "how does this feature work", the above statement is true. For critical board offline situations, the above sets alarm bells ringing loudly. Critical issues need a formal support ticketing system - which is included in the licence fee. Come to think of it, no other service I use has separate support and licence fees.
For those that wish to retain ticket support longer term, we will be unveiling a premium support option soon. No, just no.
 
I already discontinued my other IPB forums as the cost/benefit ratio slid off the scale.
A 60% price hike means I will now have to look at other options for my final licence, it would be easier if I felt any degree of trust or loyalty to Invision as I would just pony up and pay the money, however - and sadly for such a long time customer, this is far from the case. I cannot trust you as evidenced through the lifetime licence fiasco, and I feel absolutely no loyalty due to this 60% price while reducing access to critical support.
Very disappointed.
What I would like to see?
Cancel premium support plans and retain this as part and parcel of customers licences. Maintain current pricing plans for existing customers and roll out new price structure for new customers.  
 

Here in lies a pretty controversial policy.
You make a professional grade product, we choose it over free software like SMF because it's more secure and coded by professional certified developers, but we don't buy it, we never own it, it's still yours and we pay a license to make use of it.
Then the inevitable security flaws are identified and we must ensure we renew our licences to obtain the fix for what are problems that weren't created by us, if only to conform with GDPR and other legislation to keep our members data and personal information secure, never mind the inconvenience of cleaning and recovering from hacked sites.
So really we have no choice, once a self hosted forum community is installed, put aside anti-spam, IP lookups, forget Marketplace niceties, forget new feature temptations and nice to haves, the only 100% real reason is because of this.
Charging for access to security patches is just plain wrong. They should be free for at least 5 years if only as a mark of quality and pride.
Can you imagine if Microsoft charged for ongoing access to Windows security fixes and flaws?
 
UPDATED to add:
"We are looking to increase the speed of releases to a monthly release schedule so everyone gets bug fixes and new features regularly."
This a bad news for theme and app developers. More work. More time consuming localdev updates. Please improve the process of updating localdev installs so they are more robust.

@Mattwhat would you say if your barber would tell you that your haircut costs now 50% more just before they finish it, but then tell you that it's not a big deal because they didn't want to be the cheapest, just the best? I bet you would be furious and rightfully so.