Mailgun email sending not working! Laravel 7 app deployed on Heroku - laravel

I configured Mailgun for my Heroku application from the command line, so Heroku added the env. variables to the Heroku settings and I get the following error:
Client error: `POST https://api.mailgun.net/v3/sandboxfa4b1f9bc0414e2e977ba9e87270ecb2.mailgun.org/messages.mime` resulted in a `401 UNAUTHORIZED` response:
Forbidden

Related

Using Heroku CLI to get server.js live, entering-> "heroku create" getting-> "invalid credentials provided" error

Attempting to deploy API/server.js web service, w/ postgresql db, & react frontend deployment on GitHub Pages.
Performing CRUD requests and responses based on user input & submission.
Using Heroku cloud CLI for deployment of both Database & API.Webserver portions.
I type "heroku create" on CLI and I get the following in response:
"---> r#DESKTOP-MGEIQ49 MINGW64 ~/Desktop/FILES/DEV/WEBSERVICES/PERSON-RESOURCE/FRONT/[[[myname]]].github.io (master)
$ heroku create
» Warning: Our terms of service have changed:
» https://dashboard.heroku.com/terms-of-service
Creating app... !
! Invalid credentials provided.
» Warning: heroku update available from 7.53.0 to 7.60.2.
heroku: Press any key to open up the browser to login or q to exit: n....."
Genuises please advise...

Heroku giving me 500 | server error on my hosted laravel web application

I've just deployed an app and am getting the following: when i try to login or register while its working well on my local host
" Error: 500 | SERVER ERROR. "
http://blooming-gorge-99995.herokuapp.com/register

Deployment in heroku stopped working today

We are uploading an regularly with heroku-cli, but since today we receive the following error. Any ideas?
$$$ heroku war:deploy target/application.war --app appname
Uploading application.war
java -Dheroku.appName=appname -Xmx1g -Dheroku.warFile=target/application.war -jar /Users/bermeier0/.local/share/heroku/node_modules/#heroku-cli/plugin-java/lib/heroku-deploy-complete.jar
! ERROR: Server returned HTTP response code: 501 for URL: http://central.maven.org/maven2/com/heroku/webapp-runner/9.0.30.0/webapp-runner-9.0.30.0.jar
java.io.IOException: Server returned HTTP response code: 501 for URL: http://central.maven.org/maven2/com/heroku/webapp-runner/9.0.30.0/webapp-runner-9.0.30.0.jar
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1894)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
at java.net.URL.openStream(URL.java:1045)
at org.apache.commons.io.FileUtils.copyURLToFile(FileUtils.java:1456)
at com.heroku.sdk.deploy.DeployWar.<init>(DeployWar.java:29)
at com.heroku.sdk.deploy.DeployWar$1.apply(DeployWar.java:87)
at com.heroku.sdk.deploy.DeployWar$1.apply(DeployWar.java:84)
at com.heroku.sdk.deploy.utils.Main.deploy(Main.java:53)
at com.heroku.sdk.deploy.DeployWar.deploy(DeployWar.java:84)
at com.heroku.sdk.deploy.DeployWar.main(DeployWar.java:94)
▸ There was a problem deploying to appname.
▸ Make sure you have permission to deploy by running: heroku apps:info -a appname
Problem seems to be that maven central repository switched to https, see this post
Heroku released a fix for this issue. Just run
heroku update

Laravel Dusk Testing has an error on the server Curl error thrown for http POST to /session with params

I would like to ask me to try the following instructions on Plesk Server:
php artisan dusk
The following error will occur:
1) Tests\Browser\ExampleTest::testBasicExample
Facebook\WebDriver\Exception\WebDriverCurlException: Curl error thrown for http POST to /session with params: {"desiredCapabilities":{"browserName":"chrome","platform":"ANY","chromeOptions":{"binary" :".\/vendor\/laravel\/dusk\/bin\/chromedriver-linux","args":["--disable-gpu","--headless","--no-sandbox"," --verbose","--window-size=1024,768"]}}}
Failed connect to localhost:9515; Connection refused
/var/www/vhosts/fanswoo.com/fanswoo-framework/vendor/facebook/webdriver/lib/Remote/HttpCommandExecutor.php:292
/var/www/vhosts/fanswoo.com/fanswoo-framework/vendor/facebook/webdriver/lib/Remote/RemoteWebDriver.php:126
/var/www/vhosts/fanswoo.com/fanswoo-framework/tests/DuskTestCase.php:43
/var/www/vhosts/fanswoo.com/fanswoo-framework/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:192
/var/www/vhosts/fanswoo.com/fanswoo-framework/vendor/laravel/framework/src/Illuminate/Support/helpers.php:754
/var/www/vhosts/fanswoo.com/fanswoo-framework/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php: 193
/var/www/vhosts/fanswoo.com/fanswoo-framework/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:93
/var/www/vhosts/fanswoo.com/fanswoo-framework/vendor/laravel/dusk/src/Concerns/ProvidesBrowser.php:64
/var/www/vhosts/fanswoo.com/fanswoo-framework/tests/Browser/ExampleTest.php:22
I suspected that the Chrome Driver could not be executed, so I used the following command to detect:
./vendor/laravel/dusk/bin/chromedriver-linux
The return is as follows:
Starting ChromeDriver 2.43.600233 (523efee95e3d68b8719b3a1c83051aa63aa6b10d) on port 9515
Only local connections are allowed.
Indicates that ChromeDriver can be opened normally.
The code can also be detected on the local computer. Only when the dusk command is executed in Plesk Server will the error occur. May I ask what God should I continue to do or what to modify? Thank you!
The server specifications are as follows:
CentOS 7.5
PHP 7.1
DB SQLite3
Laravel Version 5.7
ChromeDriver Version 69
If you able to start chromedriver successfully, now try to access the below url with respective port.
http://localhost:{port}/status
For e.g., in above message, the server started on port 9515. Access the url in browser, http://localhost:9515/status
You should get above message indicating server is accessible with hostname as localhost
If your are not able access, then fix the specific issue

Error in Composer Identity Request

When I make a request for identity in composer, always give this error:
composer identity request -c PeerAdmin#orgx-network-xxx -u admin -s adminpw -d alice
Error: failed to request identity. Error trying to enroll user and return certificates. Error: Calling enrollment endpoint failed with error [Error: connect ECONNREFUSED 127.0.0.1:7054]
What can cause this and how can I solve it?
it looks like the Fabric CA server container on port 7054 is not started or is not listening, or not bound to that address/port.

Resources