v3.10.0 -> 3.10.1 upgrade error

julian

@FrankM See, that's where I don't see what you're seeing. When I run the same command, the certificate chain looks fine:

$ openssl s_client -connect packages.nodebb.org:443
CONNECTED(00000003)
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify return:1                     
depth=1 C = US, O = Let's Encrypt, CN = R11
verify return:1                     
depth=0 CN = packages.nodebb.org
verify return:1                     
---                                 
Certificate chain                   
 0 s:CN = packages.nodebb.org
   i:C = US, O = Let's Encrypt, CN = R11
   a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
   v:NotBefore: Sep 18 09:05:41 2024 GMT; NotAfter: Dec 17 09:05:40 2024 GMT
 1 s:C = US, O = Let's Encrypt, CN = R11
   i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
   a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
   v:NotBefore: Mar 13 00:00:00 2024 GMT; NotAfter: Mar 12 23:59:59 2027 GMT
---

julian

The only change I can share is that we disabled CloudFlare proxying roughly a day ago, so requests for packages.nodebb.org should get the actual IP now instead of the CloudFlare proxy IP.

otherhome.ca is not one of our clients, nor do we use their IP, although it does share the same first 6 digits.

sweetp

@baris, @Julian so I had to disable the plugin checking code in NodeBB/src/cli/upgrade-plugins.js to get the upgrade to finish, as it left my install in a broken state.

I commented out lines 77,78,79 and 82:

async function getSuggestedModules(nbbVersion, toCheck) {
	//const request = require('../request');
	//let { response, body } = await request.get(`https://packages.nodebb.org/api/v1/suggest?version=${nbbVersion}&package[]=${toCheck.join('&package[]=')}`);
	//if (!response.ok) {
		console.warn(`Unable to get suggested module for NodeBB(${nbbVersion}) ${toCheck.join(',')}`);
		return [];
		//}
	if (!Array.isArray(body) && toCheck.length === 1) {
		body = [body];
	}
	return body;
}

at least now my install Is working, but a better fix would be appreciated. Some kind of fallback url for packages.nodebb.org would be great. How about hosting on GitHub for example?

I still however have the Internal Error. - Oops! Looks like something went wrong! - fetch failed error on in the Admin panel > Extend > Plugins

julian

@sweetp If you want to skip plugin checking, just run ./nodebb upgrade -misb

./nodebb upgrade --help for options.

julian

I've turned on proxying of requests through cloudflare for packages.nodebb.org, let's see if that makes a difference.

huang1111

@julian
Hi, just now after you switched to CloudFlare the problem no longer occurs, but as far as I can see, now that you have switched the resolution to your source site again, your source site has a normal SSL configuration in an IPV4 environment, but not in an IPV6 environment.

julian

@huang1111 thank you, I think that may be the source of the problem. The ipv6 address must be wrong.

julian

@FrankM @sweetp I have removed the AAAA record for packages.nodebb.org. It's curious that it was even set, since the server doesn't even have an ipv6 address assigned.

sweetp

@Julian thats fixed the issue for me

julian

@sweetp

FrankM

Same here, problem solved. Thank you @julian

bh4 tech

Yes, problem solved. Thank you @julian
Btw, did you receive any DM(chat message) from nodebb hosted on domain ekk.app ?

julian

@bh4-tech yes, I did and replied.

bh4 tech

@julian Then there is some big issue in my server. ekk.app is neither getting public posts nor DMs from this server. Please guide on how I can find the cause of the problem.

Earlier had an issue with file uploads and thanks to guidance from @baris , I was able to solve the issue. Now, looking forward to you for help on this issue.