I'm trying to deploy a Laravel Application to Azure using the App Service.
Things are working pretty ok, I set the PHP version to 7.1, added the Composer extention, and added a web.config file in the public folder of my repo for supporting rewrites in IIS. After that I deployed through Git. I also set the correct environmental variables:
The only problem is, I can't connect to the Azure SQL Database. It gives me this strange Protocol Error, which I can't solve. Google only shows old answers... I hope someone can help me?
SQLSTATE[HY000]: [Microsoft][ODBC Driver 13 for SQL Server]Protocol error in TDS stream (SQL: select * from [settings]) (View: D:\home\site\wwwroot\........\resources\views\login.blade.php)
Alright, it turned out to be a corrupted instance of the Azure Web App. After deleting the App, and deploying a new clean version, it started working perfectly.
Related
I previously had a clearDb database on my Heroku app but this morning it stopped working. I then decided to destroy the database and add it again...
Problem is now i have the message "An error was encountered when contacting the add-on partner to create cleardb:ignite. Please try again later."
I tried from CLI and from dashboard, same error
I destroyed the previous database, via CLI and dashboard
My account's billing are filled.
I can add a postgre database without any problem
None of my apps can have a clearDB database, it's not just this one
Thanks a lot guys, i'm desperate !
My iOS app has suddenly started giving this error message when logging in or creating a new user in the app:
[Error]: {"code":1,"message":"Internal server error."} (Code: 1, Version: 1.15.4)
Here is the pickle. The app works fine on an earlier version (version 4.4.0) that I have on my iPad. Here I can log in and create a user, and I can add items and delete items while in sync with the server. In the new version of the app (4.4.1) nothing has changed with regards to the code on my login page. I can still fetch data from the server in the app as well, but logging in and creating a user gives the internal server error.
I got my server on Heroku and the database on MongoDB. The database is available and running. However, the server Heroku got several failed throughputs (5xx code) during a day. This says to me that something is going on with the server side of things.
Does anyone know where to turn to next? I can't seem to get my head around where the issue is rising from. I have already sent a mail to Heroku, so I'll make an update when I receive an answer.
But basically, I need help to know what would be my next step to figure out what is causing the error?
I am trying to deploy my webapp VS2015 RC1 DNX 451. Even when I validate connection and run publish I get error
Severity Code Description Project File
Error Error Code: ERROR_USER_UNAUTHORIZED
Error More Information: Connected to the remote computer ("crocus.arvixe.com") using the Web Management Service, but could not authorize. Make sure that you are using the correct user name and password, that the site you are connecting to exists, and that the credentials represent a user who has permissions to access the site. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_USER_UNAUTHORIZED.
Error Error: The remote server returned an error: (401) Unauthorized.
Googling the issue and even trying to view host forum just says make sure username and password is correct. I am getting nowhere trying various settings. Any ideas how to debug the issue?
I am using Arvixe.com as host.
You should contact Arvixe.com. They likely have some odd configuration on their servers but I would suspect they can help you resolve the issue.
Arvixe does not support Web Deploy anymore. Once they move you to their new servers Web Deploy won't be available to you. In Visual Studio you can set up a Publish with FTP instead of Web Deploy. If you're used to Web Deploy publishing your database changes, then you'll need to do those yourself with SQL scripts. Entity Frameworks has an option to produce a SQL script for a migration, so you can use that to publish your EF database changes.
Just getting started with laravel and have run into some trouble.
Before committing to using laravel I wanted to build a very basic web app to test the waters via homestead and then move that web app to a remote server in order to see how easy the process was.
So I've got homestead up and running and have built a very basic web app and it works perfectly locally.
However when I moved the laravel project onto the remote server the routing stopped working.
For example locally testProject.dev/contact takes me through to a mock 'contact us' view. However when I try that on productionServer.com/contact I'm greeted by a 403 'you do not have permission to access contact on this server'.
Am I missing something in laravel here or is this an issue with the sever setup?
Any help would be greatly appreciated. Thanks
Update -> This turned out to be an issue with another piece of software running on the server. Thanks for all the help.
We have an MVC3 site that uses the ASP.NET Membership Provider with Forms Authentication to let users onto the site. We have an Oracle database behind it.
It all works in house on development machines, test machines and deployment machines.
But at a client - they are getting the error "ORA-12154: TNS:could not resolve the connect identifier specified".
We thought this would be a simple case of a wrong config entry but all seems correct. They've also run a tnsping to the same TNS alias and it works. A connection via SQL*Plus also works. We've even got them to download a .NET connection string tester application and that connects ok using exactly the same connection string as the MVC3 site web.config has. It's only the website that comes back with this error. (note: all the tests were done from the same machine as the website is on)
Has anyone seen this before and provide some guidance on how to solve?
Thanks
The likely cause for this, from experience, is that the account under which the application is running is unable to read/access the TNSNAMES.ORA file, either due to file/folder permissions or network access permissions.