I just upgraded my glassfish server by doing asadmin> start-domain --upgrade domainname, now i cannot access the admin console. The applications in the server work fine, but the browser remains blank when trying to get into :4848, no error messages, nothing, just remains blank.
i would appreciate a response to this issue,
Thanks
First thing you might want to try is to verify the correctness of your domain.xml. You can do so by running the following command:
asadamin verify-domain-xml
If there is some inconsistency in your domain description you'll get a corresponding output.
Also, I've got a similar issue on GlassFish 3.1.2 and verify-domain-xml tests were passing successfully. In my case the problem was caused by cyrillic symbols in some resource descriptions.
Related
hoping that someone can help me with my issue. I've been trying to solve this issue for a week now and still doesn't have a solution.
Here is my issue - I'm encountering the below issue when my pipeline is publishing my application in IIS (Local IIS)
Before, it's working fine and I don't know why this happen now after re-running a new pipeline. I tried to re-install my IIS and removed all MachineKeys. But still got the same error. Also, after re-installing everything, I changed the Owner of all MachineKeys installed on my machine to my account (which is an administrator).
Also, I tried to removed this in the applicationHost.config of the inetsrv as other solution I found on the internet suggestion but still got the same issue.
But then, after searching for other solution - I found out that the command that's running on my pipeline for publishing into IIS somehow causes this issue. The password parameter.
I tried the command below, on running cmd as Administrator and removing the password parameter and it works.
appcmd.exe set site /site.name:"RTP_LoginService" -applicationDefaults.applicationPool:"RTP_LoginServiceAppPool" -[path='/'].[path='/'].physicalPath:"%SystemDrive%\inetpub\wwwroot\RTP_LoginService" -[path='/'].[path='/'].userName: -[path='/'].[path='/'].password:
But still thinking why this become an issue right now as before it's working even though there's a password parameter and I don't have any changes on the Task for publishing in my local IIS as this is a default command by the Task.
Thanks you in advance to anyone who can help me and give light to my issue I'm experiencing.
Giving Credentials of Physical Path for Virtual Machine Directory can also be the trouble for this password excluding issue. Tried to reproduce the issue and got some solution for this as mentioned below.
This problem will also rise because of the corrupted IIS Configuration Key. We need to avoid the key to be corrupted by encrypting the key in applicationhost.config file.
Create another test machine and generate configuration key.
Use that key for checking.
Exporting the key
From the working IIS server we need to export the key.
aspnet_regiis -px "iisConfigurationKey" "Your path for file.xml" -pri
Import config file from created test server
aspnet_regiis -pi "iisConfigurationKey" "Your path for file.xml"
Implement AES encryption algorithm: Replace the AES Provider which is a default encryption method element from applicationHost.config and configProtectedData and restart the server.
I got this working now. So, I fixed this issue by re-installing IIS URL Rewrite as somehow it got uninstalled on my machine. After that, it now working as expected.
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.
I've been trying to install Meteorjs on windows but error occurs. I already tried downloading another installer and restarting my computer but it doesn't work. It always pops 'failed to contact install server. Please try again' then displays the message 'One or more issues caused the setup to fail. Please fix the issues and then retry setup. For more information see the log file.'
Under that it displays '0x80070643. Fatal Error during installation.'
what to do with this?
One option is to run meteor preview for windows. Believe it is a standalone copy of meteor 1.1
https://github.com/meteor/meteor/wiki/Preview-of-Meteor-on-Windows
(this doesn't address the issue of connecting to server though because when you try to create a meteor account you get a similar error).
there definitely is a way to install through command line on windows (which annoyingly I can't remember from my other machine). Perhaps through npm...
Try to run the package as administrator.It works!
Try this guide.
Download .zip, then unzip and set path environment variable.
Recently I added email sending capability to my Meteor app, using both the email package, and the account registration APIs to send emails. The other day, after having tested this thoroughly on my dev machine, I deployed it to our production server using Meteor Up. Once deployed, I did a quick check that the email APIs were working properly, and let it be. A day or two later, I made some minor changes, wrapping these email APIs in a Meteor.defer method to speed up the UI. I tested the changes locally (all fine), and re-deployed. I also ran apt-get update on my server after seeing a notification there were some new security updates available. After doing this, the email system no longer works. I tried reverting back to my previous configuration, and it still isn't working. I'm getting a timeout error:
Exception while invoking method 'forgotPassword' Error: connect ETIMEDOUT
I was wondering if anyone had any ideas on what might be causing this timeout (a blocked port?...how can I diagnose this?). Given my SMTP port is working on my development machine, it doesn't seem to be an issue with my code, but rather either with the MUP deployment, or Ubuntu configuration. I'm not super familiar with configuring Ubuntu servers. Any suggestions on how to go about de-bugging would be greatly appreciated!
We got a similar problem, and it was solved by opening the needed port in EC2. thanks to https://kylegoslin.wordpress.com/2012/06/05/116/