After installing Wakanda Enterprise server version 2.2.1 on Ubuntu 16.04 LTS we can't open the Wakanda Server Administration page for starting a solution. Ports 4433 and 8080 have been enabled on the Ubuntu server. The page shows the Wakanda icon in the tab but the page stays blank. 

If you are experiencing issues accessing the Wakanda Server Administration page after installing Wakanda Enterprise Server, there could be a few potential reasons for the problem. Here are some troubleshooting steps you can try:

Check the Server Status: First, make sure that the Wakanda Server is running. You can do this by checking the status of the Wakanda process on your Ubuntu server. Open a terminal and run the following command:

If the Wakanda server is not running, start it using the following command:

Verify Listening Ports: Ensure that Wakanda is listening on the correct ports (4433 and 8080) for incoming connections. You can use the netstat command to check if the ports are in the "LISTEN" state:

sudo netstat -tuln | grep -E ':(4433|8080)'

If the ports are not listed or not in the "LISTEN" state, it might indicate an issue with Wakanda's configuration or the installation.

Check Firewall Settings: Verify that no firewall rules are blocking incoming connections on ports 4433 and 8080. You can temporarily disable the firewall to see if it resolves the issue. If the problem persists, re-enable the firewall and configure it to allow incoming connections on those ports.

Clear Browser Cache: Sometimes, browser cache issues can cause problems with loading web pages. Try clearing your browser's cache and cookies and then try accessing the Wakanda Server Administration page again.

Try a Different Browser: If the issue persists, try accessing the administration page from a different web browser to rule out any browser-specific problems.

Check Logs: Look for any error messages or logs related to the Wakanda server to identify any potential issues. The logs are typically located in the Wakanda server installation directory.

Update or Reinstall: Ensure that you are using the latest version of Wakanda Enterprise Server. If the issue persists, consider reinstalling Wakanda to see if it resolves the problem.

Contact Support: If none of the above steps resolve the issue, consider reaching out to Wakanda's support or community forums for further assistance. They may have encountered similar issues and can provide additional guidance.

Please note that the specific steps and solutions may vary depending on the version and configuration of the Wakanda Enterprise Server, as well as the environment in which it is installed.

Wakanda Enterprise Server Install No Server administration page

I have Oracle WebLogic server and Oracle Forms 12c on it, I configured webutil configuration file (webutil.cfg) by editing it, but when the WebLogic Administration server restarted (using startWebLogic.sh) it overrides the webutil.cfg file and restores it to its default values removing my editing in it.

My Question is how to make the webutil.cfg not changed by the WebLogic Administration server when restarted ?

webutil.cfg file is overridden when WebLogic Administration Server restated

I am setting up a new print server (Server 2016 Std, VM in VMware 6.0). I find myself needing to make the same change (e.g. check boxes to share each printer, list each printer in directory, set printer locations for several printers to the same value, etc.) over and over for each printer. Given we have over 100 printers managed by the print server, this can be a very time consuming task to right-click on each printer, make the changes, and then repeat for each printer.

I'm sure there's a way to "batch" change these settings, but I can't seem to find it in Print Management. Can anyone point me in the right direction?

Mass/Batch Changes to Printers in Print Management

I have a web application created using ReactJS , NodeJS and Mongo DB on windows. And I am facing issues while deploying the same application on a Linux Server in AWS. Is there any changes to be considered while deploying such?

Is there any changes that needs to be done for the code? Does the path declaration change on the config file?

getting such errors? ENOENT: no such file or directory, stat '/home/ec2-user/Project/Backend/Backend/client/build/index.html'"

ENOENT: no such file or directory, stat '/home/ec2-user/Project/Backend/Backend/client/build/index.html'"T

he above error there isn't usually any thing inside the code that needs to be changed. From the error you provided it seems that your build was not complete successful. it may happen because of some wrong import. when we work with multiple projects in the same ide it happens sometime. So you check if your files have any wrong import

ReactJS, NodeJS deployment issue on linux server where application was coded in windows

When I used autoSSL function I saw (at Manage SSL Hosts page) that ssl sert includes not only my example.com domain but also cpanel.example.com and so on but not include whm.example.com. How can I include whm subdomain?

administration

Trending Blogposts on administration

Popular Discussions on administration

openWakanda Enterprise Server Install No Server administration page

1

1

0

openwebutil.cfg file is overridden when WebLogic Administration Server restated

1

0

0

openMass/Batch Changes to Printers in Print Management

1

0

0

openReactJS, NodeJS deployment issue on linux server where application was coded in windows

4

1

0

openExtend cPanel's autoSSL domains list

3

0

0

PRODUCTS

QUICK LINKS

LEGAL