WildFly 8 Administration Console under Vagrant - jboss

I installed WildFly 8.2.1 under a CentOS image using Vagrant (with Virtualbox). My Vagrantfile includes a line for network forwarding and the "Welcome" page on localhost can be accessed normally in the host machine. When I try to access the Administration Console page, however, I get the following message:
An automatic redirect to the Administration Console is not currently available. This is most likely due to the administration console being exposed over a network interface different from the one to which you are connected to.
The same URL can be accessed normally when inside the VM. What do I have to do to make it work on the host computer?

Related

How to Connect Nakama Client (on unity) to a linux VM instance

i’ve created an instance that runs on a linux virtual matchine
i’ve also installed cockroachdb and nakama on that vm and started the node and nakama server there
i’m using oracle cloud infrastructure, i added security list to it to be able to access it through internet and now when try access it through the internet it shos me my server like this :
and now i dont know to to connect to this ???
i have the client in using and it doesn’t connect to it
and when i run it, it shows me this error
i also added the nakama port 7350, and the dashboard 7351 to the security list to have access to them through oci cloud and now the dashboard looks like this
where is the issue and how should i fix it ??
If you are using platform images, both Linux and Windows come with the OS firewall activated and allow very few services.
Open the ports on the OS firewall and try again.

Curity server admin console not connecting

I did a fresh installation of curity 7.1.0 on a Linux VM. it installed without any issue and started fine. However I am not able to connect it using admin console.
error:
Secure Connection Failed
An error occurred during a connection to xx.xx.xx.xx:6749. PR_CONNECT_RESET_ERROR
A RESET_ERROR often indicates a problem with the infrastructure in my experience.
You can try the following
Clear the cache of your browser
Test with a different browser
Check network settings, i.e. firewall, VPN, proxies, port openings...

How can I set up virtualbox to connect to both external internet and localhost.mysite.com server?

I am trying to use a Virtual Box VM to create a development environment I can share with a few dozen other developers. We are all on an internal network and need to connect to external web sites via proxy server. On the VM (guest) I am putting:
windows 10 64 bit
weblogic server
Several other dev tools
My requirements are:
From the guest OS I need to be able to hit the internet (ie google.com)
From the guest OS I also need to be able to open chrome and hit the server webpages running on the guest OS using mysite.com:8007/index.html.
I have modified the guest OS host file such that 127.0.0.1 maps to mysite.com. Ideally that should mean anything going to mysite.com will get resolved to 127.0.0.1.
Our proxy to reach the internet is http-proxy.mysite.com:80. I am able to connect to the internet (pages like www.google.com) as long as I enable the proxy (http-proxy.mysite.com:80) in chrome proxy settings. However I need to be able to enter mysite.com:8007/index.html in the browser and be able to load the homepage. I am able to hit the server using localhost:8007 but I need mysite.com:8007 to work since authentication cookies wont get passed correctly to localhost:8007 urls.
When I enter mysite.com:8007/index.html in chrome it keeps trying to redirect to the IP address of the host OS 10 . * . * . * and the server is not running on the Host OS.
When I enter 'curl mysite.com:8007/index.html' in a command prompt on the guest OS it actually does prints the correct response from my server (no idea why chrome is different / not respecting the host file config).
Any idea how to configure Virtual Box or chrome such that the external pages as well as the guest server pages work?
For internet access on VM, you need to configure network card as BRIDGE, NAT or NAT NETWORK. In your case NAT NETWORK will be better solution, because this will allow you bo be you VM visible in network, just like your Host.
If you have and Internal network you mus have also another card configured for VM for internal network.
To be your VM accessible from Internal Network via http... the coomputers in network have to setup DNS entry pointing to your VM.

Angular app not working in IE 9 on remote server

I have a simple angular application that works just fine when deployed on my local JBoss instance, but when I deploy the same war file in our sandboxed environment (also JBoss) the application doesn't load. Just shows up as a blank page. When viewed on Chrome or FF it works fine as well.
Not a lot to go on, but any pointers in the right direction would be very helpful.
Edit: Just another piece of info, it doesn't work locally on IE either when the address contains the computer name and not localhost. So http://localhost:8080/angularapp works but http://[machinename]:8080/angularapp does not.
In the post you don't make completely clear in what environments you've the problem (it's clear it doesn't work using IE, but does it work in all cases with Chrome and FF?).
But the problem you're experiencing when trying to access using the machine name (http://machinename:8080/...), may be caused because you've not defined properly the IP bindings in the JBoss startup: by default JBoss binds only to localhost (127.0.0.1), if you want JBoss to be accessed from any other network interface, you've to define it. That can be done using the -b parameter of the startup script (run.sh for Jboss 3.x/4.x/5.x/6.x or standalone.sh if it's JBoss 7). For example:
./run.sh -b xxx.xxx.xxx.xxx (where xxx.xxx.xxx.xxx is your server IP) will make the JBoss accessible only from that IP (and its corresponding machine name, provided is correctly defined in the DNS or /etc/hosts ...), but not from localhost.
./run.sh -b 0.0.0.0 will make the JBoss accessible from all the networks interfaces of your server.

jboss 7 as- unable to see jboss sample site or admin interface even after jboss has started

I am a newbie to working with jboss 7 as- I recently set it up on my server, and am able to start it as well.
However after starting it, when I access
http://IP_ADDRESS:8080
or
http://IP_ADDRESS:9990
Google Chrome gives an error that the page is unavailable.
How can such access be enabled? Also, I am using the startup-shutdown script for /etc/init.d as provided with jboss, do I have to modify the startup and shutdown commands in it, for enabling remote web access to the server interface?
Have you tried http://localhost:8080? If you're using the IP address of your PC it's probably the firewall that is blocking the access to it.