http://coldfusion.com logo
Join Slack
Powered by
Hi Team, I am in a bad situation for running my d...
# cfml-general
a
Hi Team, I am in a bad situation for running my dev environment up and running. My production environment is working fine in AWS ECS and now our Dev recently showed 403 error while accessing mydomain.com//CONTROL3/login.cfm Actually we have 2016 version working fine on all environment. We have checked all permission side issues and tried even 777 it didnt worked. We dont have a OS level securities like SELinux or UFW any. Need your assistance very much needed for unblocking our further work.
d
There isn't enough info here for anyone to be able to help I think.
p
Yea this is vague
j
Sounds stupid to ask, but did you mean to have 2 /'s?
r
if Apache involved, check Directory to have
Copy code
Require all granted
e
Before I say anything else, did you try starting the service? Can you verify the service is running? Did you reboot the box after you disabled SELinux? If it's AWS Linux, unless you explicitly disable SELinux, it's enabled. Here are general tips, but if you want more help, I want beer and pizza and more details
🍻 2
🍕 2
📝 2
a
"We had ColdFusion 2021 running in our production ECS cluster on AWS Fargate. Approximately 3 to 4 months ago, CF 2021 was also functioning in our non-production environment. However, last month, we attempted to redeploy our non-production environment with the exact image used in production, but our development team encountered a 403 error while accessing it. Interestingly, in our production environment, we are also running ColdFusion 2016, and when I use the same 2016 image in the non-production setup, it works fine. Could this issue be related to licensing? We are using Ubuntu 22.04 as the base image, where SELinux is not present, and UFW is disabled. We've cross-checked the permissions with production, and everything seems to be in order. Additionally, when we deploy a test.html file in the document root, it works without any issues. However, test.cfm is not functioning correctly, and we encounter a problem when accessing (mydomain.com//CONTROL3/login.cfm)." More over we are not able to get the log, is there any way to get the exact log.
Copy code
<!doctype html><html lang="en"><head><title>HTTP Status 403 – Forbidden</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 403 – Forbidden</h1><hr class="line" /><p><b>Type</b> Status Report</p><p><b>Description</b> The server understood the request but refuses to authorize it.</p><hr class="line" /><h3>Apache Tomcat/9.0.93</h3></body></html>
@Evil Ware "Haha, I see the deal now – beer, pizza, and some deep dive troubleshooting! . Once we have this sorted, I’ll owe you the best pizza order! Deal?🍕🍻
👍 1
e
Is it your license or a rented license as part of the image?. Adobe in its efforts to crack down on pirating, upon installation on your individual builds, appears to lock the license to that exact instance when it was installed. Anything more than this and someone at Adobe like @Mark Takata (Adobe) will throw strong words at me. Here is what I would do, Copy your config directory /where/ever/you/installed/ColdFusion/LIB copy the *.xml files, ie sudo cp *.xml /path/to/ColdFusion/lib/ /some/backup/folder/ Then uninstall Coldfusion, ie, sudo /opt/coldfusion2021/bin/cfuninstall -- thats the typical path. after its uninstalled, move any of the leftover contents to a backup location, ie cp -R /opt/coldfuion2021/cfusion/wwwroot /my/backup/path/for/wwwroot after its copied or moving, I highliy suggest copying, removing everything in the stall path., ie rm -rf /opt/coldfusion2021 -- This nukes everything. , now upload your cf2021 installer file and install cf2021. Check to make sure it's working as expected for a default install. Stop the service and copy everything in the backup .xml directory back to your new install of cf /lib. Note that if you used mod_JK, you must update your "secret" in your httpd config file to match. Once down, change the file ownership and directory ownership to the dedicated ColdFusion service owner, (If you have set that up) to the paths and directories, usually www-data,.. sudo chown -R /opt/Coldfusion2021 www-data.www-data . Now start the Coldfusion Service.
a
Hi Team, Finally i found the issue while checking further it is an issue with wsconfig connector issue. I haave forcefully try executing the wsconfig for Apache web server to forward its requests for .cfm (login.cfm for our case not forwarding properly )and other a specific domain name to the CF server for processing. 
./wsconfig -ws Apache -dir /etc/apache2 -vhost
👍 1
Team, Sorry for the vague information i have provide in this chat thread. Since i have already provided all the error related stuff earlier. Thought like you already aware of my issue. So sorry i have updated like and which caused issues for understanding this from your end. But i am very happy that you are trying to help me all the way possible. Cheers... have a nice weekend enjoy ....
Open in Slack
PreviousNext
Powered by