How do i fix shiny deployment issue in browser when running locally? - browser

I am running into issues deploying my shiny application. In R Studio, it states that the application has been deployed successfully, as per the image below.
Successful deployment message
However, I get "An error has occurred. The application failed to start. Contact the author for more information" when opening the application in the browser (chrome and safari).
Error in browser version of application
It also states the application is running on my shiny account.
enter image description here
Does anyone have any recommendations to what problem is occurring here that prevents the shiny app from being run in a browser? The app runs locally without any issues too.
I have all packages installed and up to date and the file directory is correct. I am not running on an SSL network either.
Thanks in advance.

Related

Heroku This site can’t be reached (DNS_PROBE_FINISHED_NXDOMAIN)

Some of my personal apps and my professional apps on Heroku are not accessible.
They don't have a custom domain linked, so I access them via http://.herokuapp.com
Most of the time, they work great, but often I receive following response from my browser
This site can’t be reached
<myapp>.herokuapp.com’s server IP address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN
The app is up and running. It does not crash (as I haven't made any changes to it in a while).
I have tried restarting all dynos, to which the log says that the app is up and running and the db is connected.
Heroku is also not reporting any of their services to being down either.
How can I resolve this issue?
I have read a similar question, but the only result coming from it was that Heroku was temporarily down. So please don't link that one again.
Update
Without any of my interference, the application can be reached again on Heroku. How is this possible if Heroku says that there were no problems with their app platforms?
And more important: is there a way to defend against this?

wkhtmltopdf as node module fails when run as windows service

I am running a node app that uses the wkhtmltopdf module (https://www.npmjs.com/package/wkhtmltopdf) and node routing to return a pdf of a page when the user navigates to a /pdf path. Everything works fine when the app is run on in the servers console, but when the app runs as a Windows service, the pdf call fails. I get the browser crash screen with the message that the site refused to connect. The rest of the site works fine, just the path to return PDFs fails, and I can't glean anything from the logs. Is this a known issue with wkhtmltopdf?
OS: Fedora
I had the issue with my node server program and wkhtmltopdf module in it, not generating pdf when run as a service. Turns out that a user for the service was set as nobody and so was usergroup. We removed that entry and reran the service it works.
I am guessing this could be the issue with Windows as well.
Please let me know if it did not work, did work or you already solved the problem with another approach.

net::ERR_CONNECTION_REFUSED when moving app from local machine to remote server

Had a look around at some other threads and there doesn't seem to be someone with this exact problem.
The problem is that I have made a webapp that works fine when hosting it locally. On the app there is a button that causes a request to be sent to my server and it performs as expected on localhost:3000 but when I host it remotely on a linux box purchased from digital ocean the site loads but the when the button is pressed I see
net::ERR_CONNECTION_REFUSED
in the console.
I'm not sure how useful it would be to post code so I will leave that out unless requested. I'm hoping this is due to some server configuration issue?
Further info:
This is a node application on a server running ubuntu. To run the application I use and keep it running I use PM2.
Thanks in advance.

Deploying lightswitch desktop application error

I am having difficulty in deploying my forst lightswitch desktop application.
when i try to publish, in the summary window it says
Database: Donot Publish
and the install.htm file is cofusing to me.
Can someone help me with a step by step tutorial.
I will be grateful.
I have installed Microsoft SQL server 2008.
The process of deploying a LightSwitch-based application differs depending on the application type and deployment scenario that you select. You have said that your lightswitch application is a desktop application. So, the possible deployment scenarios are:
Desktop client 2-tier
Desktop client, 3-tier
These links will help you :
Deploying LightSwitch Applications
How to: Deploy a 2-tier Application
How to: Deploy a 3-tier Application
You should try to get the exception info/stack trace from the server process (vslshost.exe) to get more information about the error when retrieving or saving data. If your app tries to load data when opening, change it so that there is no default screen. This will prevent the app from opening a screen when loading the app and trying to load data, allowing you enough time after opening the app to attach a debugger. You can follow my blog post at http://blogs.msdn.com/b/mthalman/archive/2013/08/16/how-to-get-a-stack-trace-in-lightswitch.aspx for info on how to get the exception info.

Windows Azure MVC3 app - 500 - Internal server error

I was running my application with no errors locally, but when added Windows Azure project, set up the database config, generated the packages and ran in stage mode, I just can get 500 internal errors.
My app has some redirections for logged and non logged users.
I tried to follow some answers about the problem with no results. When I run the application locally with the emulator everything runs ok.
I didn't set any permission or user anywhere in my SQL or Windows Azure panel. As I don't have any experience with Windows Azure, please explain steps on how to do things =)
Now, after reading almost 20 articles, I realized that I was using the old Membership and Session Providers, and that the old aspnet_regsql doesn't fit Windows Azure.
So, the first action of my application was watch if the user was logged in. Because of that, the 500 Internal errors.
Articles that helped me a lot:
http://geekswithblogs.net/ranganh/archive/2011/06/21/using-the-asp.net-membership-api-wish-sql-server--sql.aspx
http://www.hanselman.com/blog/IntroducingSystemWebProvidersASPNETUniversalProvidersForSessionMembershipRolesAndUserProfileOnSQLCompactAndSQLAzure.aspx

Resources