dotnetcore-buildpack heroku-22 support

Jun 20 '22 13:06 jincod

Hi @jincod I have a quick question, is it possible some static assets are being left out after the build process? I have some .png files in wwwroot, they've disappeared from the production build

Jul 21 '22 17:07 danirdd92

Hello @danirdd92

Please check this https://stackoverflow.com/a/62598687

Jul 21 '22 17:07 jincod

Hi @jincod Thank you for this repository. I just updated my dev environment to Heroku-22 and needed to update my .Net (to Net5.0) environment to correct deploy errors. I am now able to debug my app correctly in my local VS 2019 environment, but I am unable to deploy correctly or run in Heroku. I have investigated the libssl error and have not found any workable fixes.
I asked Heroku support to review my logs: 2022-07-31T23:10:03.000000+00:00 app[api]: Build started by user [email protected] 2022-07-31T23:11:05.829188+00:00 heroku[web.1]: State changed from crashed to starting 2022-07-31T23:11:12.043452+00:00 heroku[web.1]: Starting process with command cd /app/heroku_output && ./TheSITE 2022-07-31T23:11:13.332852+00:00 heroku[web.1]: Process exited with status 134 2022-07-31T23:11:13.200604+00:00 app[web.1]: No usable version of libssl was found 2022-07-31T23:11:13.386354+00:00 heroku[web.1]: State changed from starting to crashed 2022-07-31T23:11:05.538375+00:00 app[api]: Deploy 4de2345a by user [email protected] 2022-07-31T23:11:05.538375+00:00 app[api]: Release v247 created by user [email protected] 2022-07-31T23:13:07.000000+00:00 app[api]: Build succeeded

2022-07-31T23:15:02.458553+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mydevsite.herokuapp.com request_id=a92cc550-d758-4475-9787-99bbc00ed09b fwd="166.70.23.236" dyno= connect= service= status=503 bytes= protocol=https 2022-07-31T23:15:02.683568+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=mydevsite.herokuapp.com request_id=49972280-8cd8-41d7-b599-2ac33c1cf654 fwd="166.70.23.236" dyno= connect= service= status=503 bytes= protocol=https 2022-07-31T23:18:21.366191+00:00 heroku[web.1]: State changed from crashed to starting 2022-07-31T23:18:27.644513+00:00 heroku[web.1]: Starting process with command cd /app/heroku_output && ./TheSITE 2022-07-31T23:18:28.717088+00:00 heroku[web.1]: Process exited with status 134 2022-07-31T23:18:28.598798+00:00 app[web.1]: No usable version of libssl was found 2022-07-31T23:18:28.797036+00:00 heroku[web.1]: State changed from starting to crashed

Heroku’s reply: quote I checked for the buildpack you are using , and found its not part of officially supported buildpacks . Sorry that we dont provide much support for third party buildpacks as its against Heroku Support policy ,we suggest opening up an issue on the buildpack’s GitHub page. And I understand that you upgraded to Heroku-22 and started observing this, Thanks for the full logs and as you highlighted 2022-07-31T23:18:28.598798+00:00 app[web.1]: No usable version of libssl was found - This one we should look out for. As mentioned here, Heroku-22 stack is based on Ubuntu 22.04 ships with OpenSSL 3.0, Heroku-22 stack is based on Ubuntu 22.04 ships with OpenSSL 3.0. OpenSSL 1.1 is not available as a runtime library. If you see OpenSSL/libssl related errors (for example libssl.so.1.1: cannot open shared object file or SSL_read: unexpected eof while reading, but there will be many other variations), you will need to update your dependencies and/or third-party buildpacks to versions that are compatible with OpenSSL 3, and ensure that dependencies or binaries you use are compiled against OpenSSL 3. I suggest you to check the dependencies (and/or check about buildpack you are using by creating an issue buildpack’s GitHub page) you use are compiled against OpenSSL 3. End quote

Any help would be appreciated