I have a website made with laravel 7. I have a problem that the website is smoothly accessed but the FTP hosting and API often timeouts
I tried switching to a new server provider and the result was that the website, FTP, and API had no problems. But the old provider said it wasn't a server problem
Related
I am new to wechat development, as I can see from the documentation it requires setting up a server, getting a domain and ssl certificate. I am developing an app that sends a request to a server, fetches pdf file from database and downloads that file to user's phone. Since I am using pdf, I need to store binary data, so VPS hosting should be the best option here. But I am not sure if I can use it for WeChat, I noticed in most documentation and tutorials developers are using cloud services.
Of course.whatever serve provider is.
I have a vps, where my spring boot backend is running on. The frontend is a mobile app built with the ionic framework.
The backend is built this way: in the front there is an so called resource server, which is an graphql server, which redirects the requests to rest microservices which are behind the resource server. Every microservice has is own task, which he's responsible for. (e.g. an fileupload-server which uploads/downloads files to a database). The whole application, including the frontend is secured by an keycloak instance, which is running as an docker container like the whole application, except the frontend.
Now my questions is, we dont have a domain and for some reason they wont buy one, but we wont to secure the communications over ssl/lets encrypt. But lets encrypt isn't able to create ssl certificates for ip adresses. So finnaly my question is: do you guys, know a solution to my problem which fits?
So far,
Daniel
I'm currently developing a web apps for my client, and my development server (a shared hosting server) only support MySql. But I just came to know that my client on whose server I'm going to deploy the laravel web apps on only support Mssql.
So my question is, later when I deploy the laravel web app on my client's server, what should I do to make the web apps works perfectly well? Is it enough if I just change the default driver from mysql to sqlsrv?
Folks,
We have a website running with CodeIgniter 2.x optimized with PHP 5.3.x when it was developed some 3-4 years back. It was very stable for few years until we didn't migrate it to a new Server based with CentOS + WHM + PHP 5.5.x. I tried talking to GoDaddy if they can downgrade the server to PHP 5.3.x but they refused to do that.
Interesting is, after migration, website still running fine and users can login and browse all the functionality etc but when a request is generated to manipulate / CRUD database then nothing happens except returning to that very same page without any update. Right after a CRUD request, pressing CTRL+F5 does the magic and the request gets a success. I tried making the requests by opening Console in Chrome browser by enabling 'Disable Cache' and everything works fine.
There is no Caching is setup under CodeIgniter nor under OS / WHM etc, I'm sure about that. I'm having no clue about the scenario.
Has anyone experienced the same ever or can suggest doing something to resolve the matter.
P.S: Another website developed with same Code-base / Architecture is running perfectly on the described new server.
I have deployed a ASP.NET MVC 4 w/ SignalR application of mine which is working fine on all clients, except one. When using Chrome Dev tools to debug the page I see that the SignalR transport method is ServerSentEvents and that the SignalR GET requests have a status of 'Cancelled'. This is the case in both Chrome Latest & IE 9 Browsers.
This problem is specific to a single client. A few things I have tried are:
Disabling Windows Firewall
Adding my site to Trusted Sites with
Security settings 'Low'.
As a bit of a background on the client.. they are part of a corporate network running Windows 7. Another computer on the same network had the same issue, however, this was fixed by adding my site to 'Trusted Sites'.
AVG Internet Security was blocking these requests. Disabling 'Online Shield' meant the app returned to normal working order.