If restarting the OMU service didn't solve your issue, you can check the Blacklist/whitelist and input your IP address to be allowed:
Configuring the Blacklist and Whitelist for OMU Portal Access
This topic describes how to configure the blacklist and whitelist for OMU portal access. The blacklist and whitelist can prevent unauthorized access to and operations on OMU portal services as well as defend against common web attacks, such as the injection, cross-site request forgery (CSRF), and cross-site scripting (XSS) attacks.
Log in to the MPU server as the admin user and run the su - root command to switch to the root user.
Enter the password of the root user as prompted and press Enter.
To prevent such attacks, the Apache provides the blacklist and whitelist mechanisms. To enhance security, you are advised to configure the whitelist.
Run the cp /home/ivs_omu_portal/httpd/conf/httpd.conf /home/ivs_omu_portal/httpd/conf/httpd.bak command to back up the httpd.conf file.
Run the vi /home/ivs_omu_portal/httpd/conf/httpd.conf command to edit the httpd.conf file.
Use the whitelist. IP addresses that are not in the whitelist cannot access the OMU portal.
Modify the information between <Directory "/home/ivs_omu_portal/htdocs"> and </Directory>.
#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all
Modify the two lines as follows:
Order deny,allow
Deny from all
Allow from x.x.x.x y.y.y.y (place the whitelist here)
Save the setting and exit.
Use the blacklist. IP addresses that are in the blacklist cannot access the OMU portal.
Modify the information between <Directory "/home/ivs_omu_portal/htdocs"> and </Directory>.
#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all
Modify the two lines as follows:
Order allow,deny
Allow from all
deny from x.x.x.x y.y.y.y (place the blacklist here. x.x.x.x and y.y.y.y specifies the IP address of the attack source in the log file)
Save the setting and exit.
Run the /home/ivstool/bin/service.sh restart omuportal command to restart Apache for the settings to take effect.
If the response status 500 is displayed after the login to the OMU portal, check and correct the syntax for adding codes. Then perform 2.e to make the settings take effect.
If the error persists after the login, run the cp /home/ivs_omu_portal/httpd/conf/httpd.bak /home/ivs_omu_portal/httpd/conf/httpd.conf command to restore the settings and perform 2.e to make the settings take effect.