Replies: 6 comments 7 replies
-
I have the same problem here as well |
Beta Was this translation helpful? Give feedback.
-
I have the same problem |
Beta Was this translation helpful? Give feedback.
-
ran into this issue building in docker. added the following before build/publish RUN mkdir -p ~/.aspnet/https |
Beta Was this translation helpful? Give feedback.
-
I am traveling and cannot test until next week, but thank y'all so much for reviving this issue. I'll make sure I credit you the answers. |
Beta Was this translation helpful? Give feedback.
-
Same issue on my side |
Beta Was this translation helpful? Give feedback.
-
I recently battled with this because I was starting with a fresh development machine and wrote a quick Gist describing the issue and how it can be resolved. Thank you to the others in this thread who helped point me in the right direction: |
Beta Was this translation helpful? Give feedback.
-
I am trying to deploy a site to Azure static web apps.
I used the Azure portal to create a new Static Web App, and configured the portal options to use my github repo as shown here:
As expected, upon creation of the resource in Azure, a workflow yml file was automatically generated in GitHub, and the job ran but failed.
(I ran into an issue with Node versioning, but was able to resolve that error by being explicit in my package.json file.)
During the Build and Deploy step, I am getting the following error message:
The portion of the vite.config.js file throwing this error (out-of-the-box code):
I threw in a couple of logging messages to check that the certFilePath value was being generated in a sane way - looks fine to me but I don't know for certain that it is correct. It's showing:
/github/home/.aspnet/https/MyAppName.pem
- is this right?Can anyone tell me either why this is happening, or how I can debug this issue?
Beta Was this translation helpful? Give feedback.
All reactions