I've been trying to host Jabbr on AppHarbor.
The guide here is not up to date as Jabbr doesn't have a dependency on Janrain anymore.
Steps I have done:
Installed the SQL Express addon.
I've pushed the latest Jabbr code from GitHub to the AppHarbor.
Changed the connection string with the full connections string from
configuration.
Updated jabbr:encryptionKey and jabbr:verificationKey (as David Flower suggested).
The application manage to loads up, I can usethe default login screen, I can create a new user, but when the application crashes after login was successful (I think).
It is showing Server Error
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
When using the AppHarbor owns Errors pane, it shows nothing related.
What is the best way to debug this?
Thanks!
Ariel
Related
I'm having trouble with setting up ACORE API's and then having them work on a website.
Background:
Azerothcore running 3.3.5 on a debian standalone server, this has the Database, Core files and runs both the world and auth server basically a standard setup that is shown in the how-to wiki.
I also have a standalone web server, on the same subnet, but it's a separate server running linux and normal web server stuff, this has a wordpress installation with azerothcore plugin for user signup etc.
I'm trying to add the player map (https://github.com/azerothcore/playermap) and the ACORE-API set of functions (server status, arenastats, BG que and wow statistics) (https://github.com/azerothcore/acore-api)
Problem:
I understand the acore-api must be run in a container (docker or whatever) on the server, which I have done and it binds to port 3000, I can then go to the local ip:3000 and it brings up this error. (all db's etc are connecting and soap is working)
error 404 when navigating to IP:3000
I do get a few errors when running NPM install seen here: I'm not sure if they would be causing any issues or not.
screenshot of NPM errors on install
But further that, when I put say 'serverstatus' on the webserver (separate server) and configure the config.ts file I can't seem to get anything to display.
I'm not sure what I'm doing wrong but is the same scenario for all of the different functions for the acore-api
How are these meant to be installed and function? I feel I'm missing a vital step.
Likewise, with PLAYERMAP I have edited the comm_conf.php and set the realmd_id, but when loading the page, I do get the map, but the uptime is missing and no players are shown?
Could someone assist if possible?
Seems like an issue with NodeJS version. Update your NodeJS to latest LTS version 16.13.0 (https://nodejs.org)
I have an API in a .NET project that I'm running with Visual Studio Mac (8.4.3). I run it in release mode, and it opens a browser window with localhost:5000. The browser window says "ok". However, when I try to hit endpoints in that API, it fails very quickly. When I ran this API (ie. same code) from another server and accessed it via proxy, it ran fine. For example, when I ran it on a server whose IP was 162.250.198.98 and proxied into it, I would hit an endpoint like 162.250.198.98:3000/api/user and it would work, but now when I try to run localhost:5000/api/user, either from my app or from Postman, it fails almost instantaneously. When running it in Postman, I tried what it suggested by turning off 'SSL certificate verification' in Settings, but no change.
Can anyone advise me on how to approach troubleshooting this?
Wait, so You are saying that while trying to call API on 162.250.198.98:3000/api/user You are fine but while trying to do the same thing on localhost:5000/api/user You are getting an error? Would it might be possible You have Your API configured to receive calls at 3000? :)?
No, but really - please chech it out, maybe it is that simple, I'm couting on it :).
You can change/check it in Visual Studio: main project > Properties > Debug > App URL.
Okay, this may be involved...
Anyway, I am trying to learn how to use ASP.Net.
The environment is like this:
Windows 7 Professional
Visual Studio 2010
SQL Server 2008 Developer Edition
I am trying to follow the article here:
Developing and Unit Testing an ASP.NET MVC 2 Application - CodeProject
So far, I have installed IIS, IIS7 Manager, SQL Server and have built the solution from the article successfully.
Then, I created a limited rights user on Windows 7 and added that user to the authorized users in the SQL Server Management Studio.
After much trial / error, I can successfully connect to the (attached) database in the solution folder from the article. This was confirmed by running cmd.exe as the test user and connecting to the SQL server.
Now, when I publish the app to the "X:\inetpub\wwwroot\~user\site" directory, the page loads and looks similar to that shown in the CodeProject article here:
Patient Maintenance Screenshot - CodeProject
Except that I do not have any records shown between the "Patient Maintenance & Search" box and the "Patient Information" box. When I enter info into the query boxes and submit, the results page only shows "no records found". Clicking the "Save" or "Reset" button does nothing in Firefox.
So, I fire up IExplorer and attempt the same. This time, the error icon indicates that there are "missing objects" or "expected objects"...
Anyway, I then go to the IIS7 Manager and change the "Anonymous Authentication"\"Anonymous user identity" to the test user.
As that does nothing for me, I then open "Authentication\Basic Settings..." and change the "Connect As..." user to the test user and successfully test the connection.
Reloading the page in the browser this time results in the Server Error: "The current identity (MachineName\UserName) does not have write access to 'X:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files'."
So, I go to change the permissions on that folder, but decide to pause because I am really frustrated. After finally getting everything installed / updated this morning / afternoon - I took a nice nap... then got up and started on it again, but not so well...
But, now I fear that I may be headed down a wormhole. I don't want to continue beating my head against this and (probably) going about this the wrong way.
So, does anyone have any good links to blogs / tutorials that deal with a step by step approach to setting up an ASP.net site?
TIA
Add the account to IIS_USRS and see if that helps. If by chance, that doesn't help, you will need to download a utility called process monitor.
Link
http://technet.microsoft.com/hi-in/sysinternals/bb896645.aspx
I'm trying to use EQATEC Profiler to profile my ASP.Net app. I followed the instructions listed here. It worked the first time, but every since then, when I run my app, I don't get a "Profiled app started" message. Then when I click on the "Take snapshot" button, I get the following:
"Taking snapshot ...failed: The remote server returned an error: (404) Not Found."
Why can't it find my app?
If a profiled app encounters errors it will log these to the profiler.log file. By default you will find this in C:\Windows\Temp\EQATECProfilerLogs. Try to see if it holds some clues. You can also try to enable "Full logging" in the app options, which will at least output something to the log.
A profiled app is actually the "server" when talking to the profiler; it is the profiler that connects to the app, not the other way around. In your case it seems that the old app has stopped listening (otherwise the profiler's attempt to connect would simply be served by the old app), but the new app has not (could not?) started listening.
It seems strange, though, so my best suggestion is to examine the log-file. It will e.g. show if the app could not start its control-server and if so, why not.
1) Try rebuilding (in Equatec) your application. Make sure "enable runtime control" is enabled in the application options when you build.
1a) Try changing the port being used for runtime control.
2) Run your application through Equatec
3) Check if you have anything funny for firewall settings or similar. Some firewalls treat Equatec communication as traffic to be blocked.
4. If all else fails, just close your application normally. Even if taking snapshots fails, you can still see the profile once your application is closed.
Guess I should provide an update on this. The error was resolved once I downloaded the latest version.
I've promised to take a look at an old DotNetNuke installation for a client with the intention of making a few, hopefully minor, changes. The installation is rather old - I believe version 3.0.013 - and the production copy is running against SQL Server 2000, Windows 2003 and .Net 1.1.
As the production server is live and significantly used we need a development installation first. I have attempted to install a copy on my local server - Windows 2003, SQL Server 2005, .Net 2.0, and although with a few tweaks I can successfully get it to display the site, I cannot login, or even access the login module (ie just putting in blank username and password attempting to generate a 'must enter username' type error) without getting the error 'Object reference not set to an instance of an object'
I've spent some time trying to get around this error, without success, although I am hampered by not having used this package before.
So my questions are
Has anyone managed to run DotNetNuke 3.0.x with this configuration (or do I need to setup a box with SQL 2000 and .Net 1.0 to get it to run)?
Any suggestions where I should start looking for this error, or has anyone come across anything similar before?
EDIT: Eventually chickened out and installed in on an old webserver with Win2003/SQL 2000/Net 1.1 and it went in fine on an identical install. So I guess the answer is no, it doesn't work straight out of the box.
My feeling is that you shouldn't have any trouble running in the above mentioned environment. But taking a closer look at the error itself will help us to prove that.
If the error is occurring only when you navigate to the Login module, it may be an issue loading the authentication provider. The best way to find out is to look in the DNN Event Log and take a look at the full error message.
Because you can't login to access the Event Log, you should probably just take a look at the row created in the database when you receive the error. The table is called EventLog and there may be a little bit of friction in parsing the error message out, as all of the details are stored in the database in an XML format.
In general, when moving a site from one environment to another there are only a couple of things that you'd need to do:
make sure you can connect to the database
set the file system permissions
It sounds like you already have database connectivity because you can load the site.
However, you may want to double check (just re-apply) the file system permissions for the root of the website on the machine in question. Make sure the identity of the website (typically ASP.NET Machine Account or Network Service) has 'Modify' permissions on the root website directory. Perhaps the web site can't load a particular assembly due to lack of permissions.