Jim M

Believe it may be using the IP address of the user who your background task ran under that populates it. I can see how this may lead to confusion, I will bring this up internally. If you switch to running background tasks with cron, believe it uses the server IP address.

Did the patch work as expected and everything is fine now? If so, this may have been a temporary error with the upgrader.

Glad to hear you've found it 🙂 .

Did they fill out all fields? I was able to register without issue. I would advise checking with your email provider which you have setup in ACP -> System -> Email Settings. The email error log would simply indicate that there were no errors passing the email from our software to your provider. There could be errors after the provider has accepted it so checking with them would be your best bet. This is due to you are using HTTP, Chrome will state this for any data transmitted over a form in HTTP. If you want to get rid of this, please work with your hosting provider to add an SSL certificate to your server then follow these instructions to configure our software: https://invisioncommunity.com/4guides/advanced-options/configuration-options/using-ssl-https-r273/ This is a generic CSRF error. If this is happening to all users, you will want to disable all third party applications/plugins and switch to an unmodified theme. If this only happened to one user who may have been sitting on the login page for an extended period of time, this would be expected as the CSRF key has expired.

As Randy mentioned, this is an issue with your server reaching Facebook. If it happens temporarily, it probably is an issue on Facebook’s side but if it continues consistently, it may be on your end and you need to contact your hosting provider.

Glad to hear that reverting the template helped.

You would want to contact your hosting provider if you are unsure. The second error, if you have any modified email templates, you’ll want to revert them.

Glad you found a solution to your issue.

Sorry, what my colleague is asking is caching outside of our software. This may be something on the server.

Unfortunately, this is a network error which your server is reporting back. You would need to investigate why this is being blocked by your network. It could be the port, configuration, or more involved. I’m afraid, server management items, such as this, are outside our scope of support.

Thanks for posting! Unfortunately, this issue is beyond the scope of our technical support. 👩‍💻 Our technical support is happy to help you with the Invision Community platform, but we're unable to help with things like server management, theme questions and modifications. I've moved this to our Community Support area where other Invision Community owners will see it and help where they can.

I have moved this to a ticket so we can further assist you with this request. Please look out for an email from us with further correspondence.

I reapplied files for you, give it a minute or so and try going to /admin/upgrade

Sounds like the field above in your database is from a third party application and missing a default value. You can disable strict mode on your MySQL server to disable these checks. Please check with your hosting provider with performing it.

Sometimes the applying of files can be delayed so give it a few more moments and check /admin/upgrade again.

This would mean you have some caching on the server. If there is anything further, this may also be complicating it. It is certainly something that is frowned upon now and not allowed. However, if you have custom or older applications/plugins installed, this would not be covered under reviews. There are no means to simply review this on your own without doing tests in the same situation.

I have tagged this to a developer to review what you have found here on our community.

We support it now, yes.

If you're stuck there and have not started the upgrader yet in /admin/upgrade, you'll want to download a full set of files from the Client Area and extract those to your computer. Then upload the contents of the "ips_****" folder to your server, overwriting what is there. Once that is done, go to /admin/upgrade and follow the prompts in your browser to complete the upgrade.

Excellent. Sometimes, the unread/read tracker can get a little overwhelmed so if there is an issue clearing it helps.

Excellent. Thank you. I have moved this to a ticket so please watch your email for further correspondence.

Copying the same content from your alert, I am not seeing this but if you leave the alert up for our user, I can have this investigated further by our dev team.

Is there any caching on your community? I am seeing that the upgrade is complete but the front-end is still displaying it. If there is no caching on your server, we will need investigate your database.

Sent you one.

Unfortunately, I am not able to reproduce this myself on my test instance with the same text. Only difference is I have the patch. Could you please apply the patch in ACP -> Support then retest?