Closed franckadil closed 10 months ago
@franckadil have you executed yarn install
before yarn develop
? Another possibility is that you've updated only @strapi/strapi
and forgot to update @strapi/provider-upload-aws-s3
? Because the aws-s3 dependency has been removed.
@franckadil have you executed
yarn install
beforeyarn develop
? Another possibility is that you've updated only@strapi/strapi
and forgot to update@strapi/provider-upload-aws-s3
? Because the aws-s3 dependency has been removed.
Yes I did the usual,yarn install
, thenyarn build
before yarn develop
.
For the record I ran a separate test on my second laptop (Ubuntu 22.04 LTS, Node 18 Latest LTS) I tried the Quick Start Guide and got a similar error the start guide crashed it was complaining about styled-components , unfortunately I wasn't able to take a screen capture or the time to get the logs (I am traveling).
@christiancp100 Hi Christian, I am back at the office and I tried to give it an other try.
I was able to spot this error: 2023-12-01 15:16:59 error An unexpected error occurred: "https://registry.yarnpkg.com/@strapi/plugin-i18n/-/plugin-i18n-4.15.5.tgz: getaddrinfo EAI_AGAIN registry.yarnpkg.com". It seems like I am unable to get the 'aws-s3' plugin.
@christiancp100 Hi Christian, I am back at the office and I tried to give it an other try.
I was able to spot this error:
2023-12-01 15:16:59 error An unexpected error occurred: "https://registry.yarnpkg.com/@strapi/plugin-i18n/-/plugin-i18n-4.15.5.tgz: getaddrinfo EAI_AGAIN registry.yarnpkg.com". It seems like I am unable to get the 'aws-s3' plugin.
That's not a bug with us that's a DNS resolution failure of the yarn registry and I'm guessing an issue with your network.
@christiancp100 Hi Christian, I am back at the office and I tried to give it an other try. I was able to spot this error:
2023-12-01 15:16:59 error An unexpected error occurred: "https://registry.yarnpkg.com/@strapi/plugin-i18n/-/plugin-i18n-4.15.5.tgz: getaddrinfo EAI_AGAIN registry.yarnpkg.com". It seems like I am unable to get the 'aws-s3' plugin.
That's not a bug with us that's a DNS resolution failure of the yarn registry and I'm guessing an issue with your network.
Tested with YARN and NPM, over Debian and Alpine over 2 different networks, outside our building as well as on AWS and and Google Cloud Compute. And I am still having this issue.
@franckadil I'm sorry we can't help you on our side, but the aws-s3
dependency doesn't exist anymore on 4.15.x. If you have problems with the dependency might be because some caching or node_modules stuff
@franckadil I'm sorry we can't help you on our side, but the
aws-s3
dependency doesn't exist anymore on 4.15.x. If you have problems with the dependency might be because some caching or node_modules stuff
Thank you @christiancp100 for the information, now I am sure I am not crazy. Please can you update the site or communicate to the larger audience that the aws-s3 dependency have been deprecated?
I am using "@strapi/provider-upload-aws-s3": "^4.15.5", I have tested on 5 different machines now just to rule out a local cache or system configuration issue.
Your original error wasn't dealing with the aws-s3 package it was with i18n. The error of the address not found is not from us it's your networks inability to resolve an IP address of the yarn registry. We test these regularly (at least 4 or 5 times a week) and I have not seen this issue come up. It's almost certainly a network issue either your on VPN, behind a strict firewall, or your corporate DNS won't resolve the yarn registry address.
If you Google the string: getaddrinfo eai_again
from your error you will see the several references to that being a network problem, generally a forward corporate proxy problem.
https://stackoverflow.com/questions/40182121/whats-the-cause-of-the-error-getaddrinfo-eai-again
Specifically the eai_again
stems from a DNS lookup timeout.
This is a templated message
Hello @franckadil,
Thank you for reporting this bug, however we are unable to reproduce the issue you described given the information we have on hand. Can you please create a fresh project that you are able to reproduce the issue in, provide clear steps to reproduce this issue, and either upload this fresh project to a new GitHub repo or compress it into a .zip
and upload it on this issue?
We would greatly appreciate your assistance with this, by working in a fresh project it will cut out any possible variables that might be unrelated.
Please note that issues labeled with status: can not reproduce
will be closed in 14 days if there is no activity.
Thank you!
Your original error wasn't dealing with the aws-s3 package it was with i18n. The error of the address not found is not from us it's your networks inability to resolve an IP address of the yarn registry. We test these regularly (at least 4 or 5 times a week) and I have not seen this issue come up. It's almost certainly a network issue either your on VPN, behind a strict firewall, or your corporate DNS won't resolve the yarn registry address.
If you Google the string:
getaddrinfo eai_again
from your error you will see the several references to that being a network problem, generally a forward corporate proxy problem.https://stackoverflow.com/questions/40182121/whats-the-cause-of-the-error-getaddrinfo-eai-again
Specifically the
eai_again
stems from a DNS lookup timeout.
Thank you for your input on the issue. But I am not using a corporate Firewall, private network, and all my tests appart from the ones I ran on Public cloud infrastructure use Google and Cloudflare Global DNS. I have stumbled on the same article since my first step was to check if my containers had access to Internet .
Team members have diligently tested 4.15.5 and they have had the same issue.
I had to revert to 4.14.5 to continue working.
I would suggest you try testing in a fresh clean project as it could be a customized yarn config or global config.
Here is my attempted reproduction on a fresh v4.15.5 project: https://www.loom.com/share/a93cc4153fad414cbec160b537f5221a?sid=718427cc-a5bd-47a4-bec9-534c77c78584
Hello!
As we have not received any new or updated information to reproduce this issue in the last 14 days we are marking this issue as closed. Should you have new information please feel free to respond and we will consider reopening it.
If anyone else have updated information for this issue, please open up a new bug report and simply reference this closed bug report so that we can get any new information you may have. If you have questions please refer to the contributor's guide on opening issues.
Thank you and have a great day!
Bug report
Required System information
Describe the bug
Can't start Strapi with
yarn develop
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Code snippets
Additional context
Since I received a lot of conflicting thoughts about the probability of having a network issue of some sort, I wanted to perform a test in order to share the steps to reproduce this error.
I will use on this test a fresh WSL2 using Ubuntu 22.04 with the same System information indicated above, on a 7th computer based at a friend's home.
I am building a docker image based on node:18.18.2-alpine and installing successful Strapi 4.15.5 without any plugin in order to rule out any system configuration issue or caching conflicts. This will allow the test to run on a containerized environment that have been used with other containers to share a bridged network with Internet access using Google Public DNS.
Docker Build Log:
Upon building and starting the Admin interface the containers exit with the following error
Error: Cannot find module 'aws-s3'
:Reverting to Strapi 4.14.5 seems to be the only workaround for now.